Well, i'm +0 on the manifest.mf solution but the issue stays the same since you still get the same parent.
URLClassLoaderFirst didnt break tests/tcks it seems, now we need further tests to adjust our common lib usage i think (mf for instance) Another alternative (maybe for 2.0) would be to get our own server classloader used only for our stuff but it would change a lot of our code and will be impacting for apps relying on openejb libs. Le 15 mai 2013 01:02, "Jonathan Gallimore" <[email protected]> a écrit : > I'd be in favour of seeing Romain's URLClassLoaderFirst option. I'm not > sure about changing the default setting though. Perhaps we could look for > clashing libraries as part of the scan when deploying an application and > throw up an appropriate warning steering users towards the new setting if > they run into problems? > > Davide's suggestion of the JBoss 7 style classloader is an interesting one. > I'm not a big fan of the JBoss/modules structure myself, but I can > understand the appeal. I can imagine it wouldn't be too difficult to write > something to parse the jboss-deployment-structure.xml file and add the > necessary entries to the classpath of the application. Would be great for > existing JBoss / Wildfly users looking to give TomEE a try. > > I would have thought we could also provide support for skinny wars/ears by > allowing Class-path entries in MANIFEST.MF where they are either looked up > from a directory within TomEE, or specified like Class-path: > ${catalina.home}/modules/mymodule.jar. > > Just a thought. Happy to have a go at working on any of these if anyone > likes any of these ideas. > > Jon > > > On Tue, May 14, 2013 at 10:57 PM, Romain Manni-Bucau > <[email protected]>wrote: > > > It would be as easy as what we have today but 2 points: > > * we dont love osgi (thats what i feel at least) - each for > > differents.reason but if we should go for it we'd end with geronimo > > * (personal) jboss module is just an osgi like and solves as much issues > as > > it creates. A strength of tomee is to be simple and understandable by any > > java guy (far to be the case in jboss or wildfly) > > > > Said in very condensed and very personal way: using such a solution for > > tomee would mean i ll go with deltaspike in tomcat/jetty > > > > Ps: never said jboss module was bad, it just doesnt match what i need and > > want under my apps > > Le 14 mai 2013 22:11, "middleware" <[email protected]> a > > écrit : > > > > > The classloader in Jboss AS 7 is in my opinion a very good > > implementation. > > > It's base on modules instead of using the more familiar hierarchical > > class > > > loading. It's very neat and in my experience it put an end to jar hell > > > > > > https://docs.jboss.org/author/display/AS7/Class+Loading+in+AS7 > > > > > > I hope my suggestion could became handy, even though I suspect it might > > be > > > not easy to implement it in TomEE > > > > > > > > > > > > -- > > > View this message in context: > > > > > > http://openejb.979440.n4.nabble.com/tomee-next-classloading-tp4662907p4662953.html > > > Sent from the OpenEJB Dev mailing list archive at Nabble.com. > > > > > >
