module jars vs WEB-INF/lib jars (issue 10039)

[Bobby Bissett - Javasoft]

This issue has bounced around a little and I don't know whom to give  
it to now. It's not an asupgrade bug since it can happen even without  
asupgrade. Please see my "Nov 2" comments here:

https://glassfish.dev.java.net/issues/show_bug.cgi?id=10039

Can I at least get a ruling of whether or not it's a valid test case?  
Can someone deploy an app that bundles a different version of  
something that's already in the modules dir?

Thanks,
Bobby


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Hong Zhang]

I think it should be ok to bundle the same library jar in the WEB-INF/lib as the one that's already provided by the system. And depending on the value of the delegate flag, the parent classloader or the WebappClassLoader will used to load the library.


Looking at the stack trace, it's from ClassLoaderHierarchyImpl.createApplicationParentCL. Maybe Sahoo could help with this one?

0400|WARNING|glassfish|org.jvnet.hk2.osgimain|_ThreadID=11;_ThreadName=Thread-3;|Exception
while starting bundle com.sun.enterprise.osgi-adapter [130]
org.osgi.framework.BundleException: Activator start error in bundle com.sun.enterprise.osgi-adapter
[130].
at org.apache.felix.framework.Felix.activateBundle(Felix.java:1750)
at org.apache.felix.framework.Felix.startBundle(Felix.java:1621)
at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:890)
at org.jvnet.hk2.osgimain.Main.start(Main.java:124)
at org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:667)
at org.apache.felix.framework.Felix.activateBundle(Felix.java:1699)
at org.apache.felix.framework.Felix.startBundle(Felix.java:1621)
at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1076)
at org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:264)
at java.lang.Thread.run(Thread.java:637)
Caused by: com.sun.enterprise.module.ResolveError: Not able to locate a unique module by name
org.glassfish.jsftemplating
at
com.sun.enterprise.v3.server.ClassLoaderHierarchyImpl.createApplicationParentCL(ClassLoaderHierarchyImpl.java:166)


Bobby Bissett wrote:

This issue has bounced around a little and I don't know whom to give  it to now. It's not an asupgrade bug since it can happen even without  asupgrade. Please see my "Nov 2" comments here:

https://glassfish.dev.java.net/issues/show_bug.cgi?id=10039

Can I at least get a ruling of whether or not it's a valid test case?  Can someone deploy an app that bundles a different version of  something that's already in the modules dir?

Thanks,
Bobby


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...