You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to suggest correcting the values of mainClass in pom.xml files in tutorial/jms module which have this element.
java.lang.ClassNotFoundException occured when I executed jar files generated after building simple module in tutorial/jms module following the tutorial. (I used appclient command of GlassFish)
This was resolved by modifying the value of mainClass element. For example,
jakartaee-examples/tutorial/jms/simple/asynchconsumer/pom.xml contains the following:
jakarta.examples.tutorial.asynchconsumer.AsynchConsumer
The correct class name would be jakarta.tutorial.asynchconsumer.AsynchConsumer.
Other child modules than simple in tutorial/jms, too, seem to have incorrect mainClass value which does not match with the name of corresponding main class. An extra "examples" part as a fully-qualified class name for mainClass element if any.
Thank you,
The text was updated successfully, but these errors were encountered:
I would like to suggest correcting the values of mainClass in pom.xml files in tutorial/jms module which have this element.
java.lang.ClassNotFoundException occured when I executed jar files generated after building simple module in tutorial/jms module following the tutorial. (I used appclient command of GlassFish)
This was resolved by modifying the value of mainClass element. For example,
jakartaee-examples/tutorial/jms/simple/asynchconsumer/pom.xml contains the following:
jakarta.examples.tutorial.asynchconsumer.AsynchConsumer
The correct class name would be jakarta.tutorial.asynchconsumer.AsynchConsumer.
Other child modules than simple in tutorial/jms, too, seem to have incorrect mainClass value which does not match with the name of corresponding main class. An extra "examples" part as a fully-qualified class name for mainClass element if any.
Thank you,
The text was updated successfully, but these errors were encountered: