We are using mule (enterprise edition) and are debating whether to use EE jars (whenever available) or CE jars. Is there a reason to go one way or another. The application is eventually going to deployed in Mule Enterprise edition.
You need to use the EE jars in order to have the EE versions of the XML schemas to resolve properly.
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.
When a Mule project is created by the Anypoint Studio itself, the IDE will generate the maven pom file with all compatible dependencies. But I want to get MuleSoft dependencies (Ex: Connectors, Munit module dependencies, etc) and their compatible versions which suit the Runtime Environment from Outside or manually - not through the IDE. For example, if a new RunTime version '4.5' is released in the future, I want to know all the compatible and new dependency versions which go hand in hand with the Runtime 4.5. This should not through the IDE. Better to have a repository or any documentation.
In Studio 7.x (compatible with Mule 4.x) it tries to select versions of connectors that are are more o less up to date with that release, but it is always recommended to use the last version of each connector that is compatible with the Mule Runtime version used. For that you can look to the release notes page to find the compatibility of each connector released by MuleSoft. Each version release usually mentions what is the minimum compatible Mule version.
Also Studio 7 has a button in the toolbar to detect updated connectors and modules and gives the option to update them.
Just to be clear, Mule 4.x doesn't have any dependencies in the pom of a Mule 4 application project. The dependencies there are needed by your application, not by the Mule Runtime.
Installed Anypoint studio configured it to use Mule 3.4, imported my flows and now when I select "run as" to test them I get an error saying I do not have a licence for data mapper even though I do not use the data mapper in the flows that I have imported from mule studio.
Can I disable or remove the data mapper component from Anypoint so I can run my imported flows (which where developed and work in Mule studio)?
You probably still have a reference to EE artifacts in the pom.xml. Or to EE schemas in the Mule XML configs. Or both...
Make sure to only refer to CE artifacts and schemes only.
I am new to glassfish. When I add Glassfish server in Eclipse Juno, I have to choose between Glassfish 3.1 and 4.0 server, which is better supported? which specific features do they have?
This is what I saw in glassfish doc:
GlassFish 4.0 is intended to be the next major release in Project
GlassFish. This release will implement the Java EE 7 specifications,
contribute to the Java EE 7 Reference Implementation and Development
Kit. The release is being designed with primary focus on the following
features :
Higher Productivity
HTML5 Support
GlassFish 3.x supports Java EE 6. GlassFish 4.0 will support Java EE 7. A vast majority of new features in GlassFish 4.0 are actually Java EE 7 features. To find out what's new in Java EE 7, register for next week's Java EE 7 Live Launch Event and you can learn what's new.
GlassFish 4.0 is nearly final. Wait a few days (literally only a few more days) and you'll be able to download the final release of GlassFish 4.0.
IMHO, just use GlassFish 4.0. FYI, the early builds of Eclipse Keplar already have support for Java EE 7 projects and GlassFish 4.0. The Juno GlassFish plugin will also be updated to support GlassFish 4.0. We'll also update the GlassFIsh IDE Plugins page next week with more information.
Glassfish 3.1 - Java EE 6 compliant server.
Glassfish 4.0 - Java EE 7 compliant server.
I have an EJB 2.1 project, works on WebShere 7. I must migrate it to WebSphere 8.
Which one is the better (less effort) approach:
First convert the project into an EJB3.1 project then migrate into Websphere. If yes, is it easy to do that by a large project?
Adapt the project till it works on Websphere8 (What should be taken into account)
Thanks??
The easiest approach is to do nothing: WebSphere Application Server v8 supports EJB 2.1 just as well as v7. Why risk changing something that isn't broken?