I have changed the mule runtime from EE 3.7.0 to CE 3.5.0 but getting error
Exception in thread "main" java.lang.IllegalArgumentException:
Application name not specified.
If you still are facing this problem, consider trying these possible solutions:
Clean your project
Update the version of the embedded server
Try creating the application again
Related
While deploying my Mule project with Mule runtime 4.3.0 to cloudhub through maven, i am getting below exception:
Execution default-deploy of goal org.mule.tools.maven:mule-maven-plugin:3.3.5:deploy failed: MessageBodyReader not found for media type=application/json;charset=utf-8, type=class org.mule.tools.client.arm.model.AuthorizationResponse, genericType=class org.mule.tools.client.arm.model.AuthorizationResponse.
Any help will be appreciated.
Thanks
Vikas
The fact that it works with Java 8 indicates it is some Java compatibility issue.
Mule Maven Plugin supports only until Java 11. See the release notes for your version to see software compatibility: https://docs.mulesoft.com/release-notes/mule-maven-plugin/mule-maven-plugin-release-notes
Facing the below issue when trying to invoke java code from javascript adapters with Mobilefirst 8.0.
Sample code from the below link is used for testing.
https://github.com/MobileFirst-Platform-Developer-Center/Adapters/tree/release80
Project structure
com.ibm.mfp.server.js.adapter.internal.JavascriptManagerImpl E FWLST0904E: Exception was thrown while invoking procedure: subtractTwoIntegers in adapter: UsingJavaInJavaScriptAdapters
org.mozilla.javascript.EcmaError: TypeError: [JavaPackage com.sample.customcode.Calculator] is not a function, it is object. (UsingJavaInJavaScriptAdapters-impl.js#24)
at org.mozilla.javascript.ScriptRuntime.constructError(ScriptRuntime.java:3951)
at org.mozilla.javascript.ScriptRuntime.constructError(ScriptRuntime.java:3929)
at org.mozilla.javascript.ScriptRuntime.typeError(ScriptRuntime.java:3962)
at org.mozilla.javascript.ScriptRuntime.typeError2(ScriptRuntime.java:3981)
at org.mozilla.javascript.ScriptRuntime.notFunctionError(ScriptRuntime.java:4036)
at org.mozilla.javascript.ScriptRuntime.notFunctionError(ScriptRuntime.java:4024)
at org.mozilla.javascript.ScriptRuntime.newObject(ScriptRuntime.java:2502)
This normally happens when your server is running a version of Java that is different from the one with which the adapter was built.For example, MFP server is running on JDK 1.7, while the adapter has been built using JDK 1.8.
Ensure your server is running the same version of Java that is used to build the adapters.
We are migrating CXF version 2.7.7 to 3.1.8 and facing the belows issue.
And also updated javax.rs.ws 2.0-m10 to 2.0.1
Exception in thread "main" java.lang.NoClassDefFoundError: javax/ws/rs/client/ClientException
If we are using the same javax.rs.ws 2.0-m10, facing the below issue
Exception in thread "main" java.lang.NoClassDefFoundError: javax/ws/rs/core/NoContentException
Anyone have the solution, what could be the right version of Javax-rs-ws version which contains both the classes?
From the CXF 3.1.x migration guide
Support for using JAX-WS 2.1 based API jars has been removed. Java 7
(now required) includes JAX-WS 2.2 so this should not be an issue.
When I am starting the JBoss server with kie workench 6.4 war file, I am getting the following error
Caused by: org.eclipse.jgit.dircache.InvalidPathException: Invalid path: social-files/<system>
Ok, since your system is Windows and you are using Wildfly this might be caused by a CDI bug that the combination introduces. I recommend you either change the operating system or try another container for the war.
Configuration: Eclipse (Juno) 4.2.2
IBM Worklight version: 6.2.0.01
Java version:
java version "1.7.0_71"
Java(TM) SE Runtime Environment (build 1.7.0_71-b14)
Java HotSpot(TM) 64-Bit Server VM (build 24.71-b01, mixed mode)
JDK: jdk1.7.0_71.jdk
Java Compiler: 1.7
My worklight studio was previously working and suddenly stops working after I had to force quit my eclipse. Even after reinstallation of the plugins, the error still recurs.
Here's a screenshot of the initial error log before 'Worklight server failed to start' and 'Failed to deploy application in the worklight server'. Any help to fix this issue will be deeply appreciated. Worklight studio issues like this is starting to get frustrating.
I uninstalled java from my mac. Reinstalled Java (JDK & JRE), new Eclipse (Juno 4.2.2) -> Then installed IBM Worklight Studio plugin. Figured it was the problem with Java as it was throwing the java exception 'unable to read the manifest'. Probably there was some issue after updating to Yosemite.
I had the same problem. You need to set correct IP for Worklight server. It doesn't work with "localhost" or "*".
It looks Java EE got corrupted somehow,
So as suggested the best approach would be to use a fresh Eclipse instance with a new plug-in installation and a new workspace as well. This way it makes sure everything is fresh and new.