Is OAS 2.0 or 3.0 specification is supported in Mule runtime 3.9? If yes, please let me know the configuration and requirement.
Only Mule 4.x and Studio 7.x support OAS 2.0 and OAS 3.0. Technically speaking it is the APIKit module for Mule 4 that support OAS rather than the Mule runtime. That version of APIKit is not compatible with Mule 3.x.
Related
I am using Mule 3.9 with Anypoint studio 7.2 for API development. After my functionality developed I was able to export to a Jar file which I was supposed to run on my hardware which doesnt support x64 architecture.
I got error of not supported architecture. So I am looking for solution in 2 ways.
As hardware architecture cant be changed, is there any way to still run Mule program on it without using Mule runtime environment.
Using exported Jar file is it possible to use it only without Mule installed on my hardware machine.
Thanks in advance.
As per comment See error message,when tried to run in Docker also.
Mule uses the Java Service Wrapper to bootstrap the Mule runtime. At this time the version of the wrapper included with Mule previous to Mule 4.4 doesn't support aarch64 as an architecture, only 32 bits ARM (armhf). At this time only Mule 4.4 Enterprise Edition seems to has compatibility with armhf-64. You should try that version to see if aarch64 is recognized as armhf-64.
Also note that Studio 7.x is not compatible with Mule 3.x applications so it is not possible to use it to develop a Mule 3.9 application. You are saying that the deployment file is a jar file so it is clearly a Mule 4 application. A Mule 4 application can not be deployed to a Mule 3 server, they are not compatible.
Which component of Mule 4.1 replaces Mule 3.9 <timer-interceptor> ?
None. Mule 3 interceptors are not supported in Mule 4. You might rbe able to replace them somewhat with custom policies, as mentioned in the migration documentationhttps://docs.mulesoft.com/mule-runtime/4.1/migration-core
The reason is that Mule 4 architecture is very different in thread management and it doesn't allow the interceptors implementation.
I use NetStandard project instead of PCL class for my Xamarin.Forms 2.4 project. I was thinking using Xamarin.Auth to store token receive with MSAL and user info locally but the nuget is not compatible with NetStandard yet.
Do we have some alternative? Can we "force" install it in NetStandard project?
Thanks,
Xamarin.Auth is being rewritten to add support for 1.0 and 1.1. Some OAuth grants like PKCE will be forced to use 1.3 and above.
There is 1.6 version of the PCL library. Lowering .NET Standard version to less than 1.6 required too much effort, so .NET support is being added with some other features.
Do you know if SAP Connector 3.0 (Nco 3.0) support .NET framework 3.5? Or it only supports 4.0 or later?
The current NCo can be downloaded for .Net 2 (compatible to .Net 3.5) and .Net 4. Separate Assemblies for the Net Framework versions and for x86 and x64, so make sure to grab the right one.
I was using NInject WCF extension 2.2 in my application, but after upgrading the Ninject version to 2.3, it stops working and return some serialization error. Is there any upgraded version of WCF extension for 2.3 or i've to use Ninject 2.2.
Thanks
Ninject 2.3 is not a released version. It requires Ninject.Extensions.WCF 2.3 found at github or on the build server teamcity.codebetter.com