Scott M Stark wrote:
Thanks for the trace log output. The source of the issue is that there are two independent deployments that have the org.eupki.ca.ejb.services.CRLFactory class:
deploy/eupki-ca-archive.jar deploy/eupki-ca.ear/eupki-ca.sar
The eupki-ca-archive.jar has precedence over the eupki-ca.ear/eupki-ca.sar in terms of preferred ordering. This means that the classes should be coming from the class loader associated with the eupki-ca-archive.jar, however, when the CRLFactory class is loaded during service creation, there is a recursion into the class loading layer to loads its CRLFactoryMBean interface that is interferring with the loading precedence and the end result is:
CRLFactoryMBean is loaded by the class loader of: eupki-ca-archive.jar
CRLFactory is loaded by the class loader of: eupki-ca.ear
CRLFactory$CertScanner is loaded by the class loader of: eupki-ca-archive.jar
I have to look more into the precedence problem, but the workaround it to only have the CRLFactory class in one deployment scope.
------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01 _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
