Thanks for the link. Exactly that link did not catch my attention as I was searching the wiki :-(
But as I am diving into this issue I guess I know what to do to resolve. Repackage the ear. I have already done so and it is bringing me further.
With respect of this beeing the JNDI forum:
I have classes that really are shared among the two jars: app-web.war and app-ejb.jar. Would it be approriate to let those classes to into one single jar, say app-shared.jar, that is then put into the ear? This would give them a "unique identity" with respect of the class loader right?
Thanks in advance. You helped me alot already.
If the class is meant to be used by both the war and the ejb-jar, the way i package it is - i create a separate jar (common-util.jar maybe) and make it available to both the war and ejb modules by specifying the common-util.jar as java module in the application.xml file of the ear. You can find more details about the same at:
The common-util.jar will be loaded by a single classloader and will be made available to both the war and the ejb-jar.
Yup, exactly what I would suspect to happen. Thanks for link. It was exactly what I was trying to do. No more classloading problems whatsoever. Simple put: GREAT. Thanx
Best wishes and regards