Re: failling tests
Just built off trunk, so working for me [INFO] Apache OpenEJB SUCCESS [7.382s] [INFO] OpenEJB :: Dependencies ... SUCCESS [0.201s] [INFO] OpenEJB :: Dependencies :: MBean Annotation API ... SUCCESS [4.583s] [INFO] OpenEJB :: iTests . SUCCESS [0.186s] [INFO] OpenEJB :: iTests :: Beans SUCCESS [6.425s] [INFO] OpenEJB :: iTests :: Servlets . SUCCESS [1.068s] [INFO] OpenEJB :: iTests :: Client ... SUCCESS [10.351s] [INFO] OpenEJB :: iTests :: Interceptor Beans SUCCESS [0.786s] [INFO] OpenEJB :: iTests :: App .. SUCCESS [2.234s] [INFO] OpenEJB :: iTests :: Web .. SUCCESS [1.452s] [INFO] OpenEJB :: Container .. SUCCESS [0.242s] [INFO] OpenEJB :: Container :: Loader SUCCESS [2.233s] [INFO] OpenEJB :: Container :: JPA Integration ... SUCCESS [2.172s] [INFO] OpenEJB :: Container :: API ... SUCCESS [0.745s] [INFO] OpenEJB :: Container :: Java Agent SUCCESS [0.612s] [INFO] OpenEJB :: Container :: Java EE ... SUCCESS [41.398s] [INFO] OpenEJB :: Container :: Java EE Accessors . SUCCESS [9.036s] [INFO] OpenEJB :: Container :: Core .. SUCCESS [12:19.537s] [INFO] OpenEJB :: Server . SUCCESS [0.077s] [INFO] OpenEJB :: Server :: Client ... SUCCESS [8.288s] [INFO] OpenEJB :: Server :: Core . SUCCESS [7.009s] [INFO] OpenEJB :: Server :: Multicast Discovery .. SUCCESS [40.284s] [INFO] OpenEJB :: Server :: EJBd . SUCCESS [1:52.201s] [INFO] OpenEJB :: Server :: Hsql . SUCCESS [1.361s] [INFO] OpenEJB :: Server :: Http . SUCCESS [2:26.130s] [INFO] OpenEJB :: Server :: Webservices .. SUCCESS [3.256s] [INFO] OpenEJB :: Server :: CXF Transport SUCCESS [2.051s] [INFO] OpenEJB :: Server :: CXF .. SUCCESS [25.343s] [INFO] OpenEJB :: Server :: REST . SUCCESS [1.614s] [INFO] OpenEJB :: Server :: CXF RS ... SUCCESS [1:04.169s] [INFO] OpenEJB :: Server :: Daemon ... SUCCESS [1.191s] [INFO] OpenEJB :: Assembly ... SUCCESS [0.046s] [INFO] OpenEJB :: Assembly :: Standalone . SUCCESS [18.565s] [INFO] OpenEJB :: iTests :: Failover EJB . SUCCESS [0.389s] [INFO] OpenEJB :: Arquillian Adaptors Parent . SUCCESS [0.043s] [INFO] OpenEJB :: Arquillian Adaptors Parent :: Common ... SUCCESS [3.305s] [INFO] OpenEJB :: TomEE .. SUCCESS [1.008s] [INFO] OpenEJB :: TomEE :: Util .. SUCCESS [1.047s] [INFO] OpenEJB :: Utils .. SUCCESS [0.046s] [INFO] OpenEJB :: Utils :: Provisionning . SUCCESS [7.549s] [INFO] OpenEJB :: Arquillian Adaptors Parent :: TomEE Common SUCCESS [3.878s] [INFO] OpenEJB :: iTests :: Failover . SUCCESS [2:43.317s] [INFO] OpenEJB :: Maven Plugins .. SUCCESS [2.406s] [INFO] OpenEJB :: Maven Plugins :: TomEE Maven Plugin SUCCESS [9.731s] [INFO] OpenEJB :: TomEE :: Common SUCCESS [20.971s] [INFO] OpenEJB :: TomEE :: Loader SUCCESS [1.769s] [INFO] OpenEJB :: TomEE :: JDBC .. SUCCESS [13.652s] [INFO] OpenEJB :: TomEE :: Catalina .. SUCCESS [13.827s] [INFO] OpenEJB :: TomEE :: MyFaces ... SUCCESS [1.820s] [INFO] OpenEJB :: TomEE :: TomEE Embedded SUCCESS [42.839s] [INFO] OpenEJB :: Maven Plugins :: Util .. SUCCESS [1.183s] [INFO] OpenEJB :: Maven Plugins :: TomEE Embedded Maven Plugin SUCCESS [12.611s] [INFO] OpenEJB :: Maven Plugins :: OpenEJB Embedded Maven Plugin SUCCESS [7.797s] [INFO] OpenEJB :: Maven Plugins :: TomEE Webapp Archetype SUCCESS [0.466s] [INFO] OpenEJB :: Maven Plugins :: jars.txt Maven Plugin . SUCCESS [1.184s] [INFO] OpenEJB :: Container :: JUnit . SUCCESS [14.153s] [INFO] OpenEJB :: Server :: ActiveMQ . SUCCESS [1.286s] [INFO] OpenEJB :: Server :: Derby Network Service SUCCESS [2.719s] [INFO] OpenEJB :: Server :: Axis . SUCCESS [5.425s] [INFO] OpenEJB :: Server :: Common CLI ... SUCCESS [6.550s] [INFO] OpenEJB :: Server :: SSH .. SUCCESS [4.604s] [INFO] OpenEJB :: Server :: BoneCP ... SUCCESS [7.109s] [INFO] OpenEJB :: Examples :: @AccessTimeout (Meta) .. SUCCESS [12.522s] [INFO] OpenEJB :: Examples :: @AccessTimeout . SUCCESS [6.760s] [INFO] OpenEJB :: Examples :: Alternate
Re: failling tests
Hi Andy, great to see :) we basically fixed all the issue on OWB side and TomEE one (one was still here this morning but only visible with profile all-adapters activated) I think we should be good tomorrow (build + TCK) *Romain Manni-Bucau* *Twitter: @rmannibucau https://twitter.com/rmannibucau* *Blog: **http://rmannibucau.wordpress.com/*http://rmannibucau.wordpress.com/ *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2013/5/13 AndyG andy.gumbre...@orprovision.com Just built off trunk, so working for me [INFO] Apache OpenEJB SUCCESS [7.382s] [INFO] OpenEJB :: Dependencies ... SUCCESS [0.201s] [INFO] OpenEJB :: Dependencies :: MBean Annotation API ... SUCCESS [4.583s] [INFO] OpenEJB :: iTests . SUCCESS [0.186s] [INFO] OpenEJB :: iTests :: Beans SUCCESS [6.425s] [INFO] OpenEJB :: iTests :: Servlets . SUCCESS [1.068s] [INFO] OpenEJB :: iTests :: Client ... SUCCESS [10.351s] [INFO] OpenEJB :: iTests :: Interceptor Beans SUCCESS [0.786s] [INFO] OpenEJB :: iTests :: App .. SUCCESS [2.234s] [INFO] OpenEJB :: iTests :: Web .. SUCCESS [1.452s] [INFO] OpenEJB :: Container .. SUCCESS [0.242s] [INFO] OpenEJB :: Container :: Loader SUCCESS [2.233s] [INFO] OpenEJB :: Container :: JPA Integration ... SUCCESS [2.172s] [INFO] OpenEJB :: Container :: API ... SUCCESS [0.745s] [INFO] OpenEJB :: Container :: Java Agent SUCCESS [0.612s] [INFO] OpenEJB :: Container :: Java EE ... SUCCESS [41.398s] [INFO] OpenEJB :: Container :: Java EE Accessors . SUCCESS [9.036s] [INFO] OpenEJB :: Container :: Core .. SUCCESS [12:19.537s] [INFO] OpenEJB :: Server . SUCCESS [0.077s] [INFO] OpenEJB :: Server :: Client ... SUCCESS [8.288s] [INFO] OpenEJB :: Server :: Core . SUCCESS [7.009s] [INFO] OpenEJB :: Server :: Multicast Discovery .. SUCCESS [40.284s] [INFO] OpenEJB :: Server :: EJBd . SUCCESS [1:52.201s] [INFO] OpenEJB :: Server :: Hsql . SUCCESS [1.361s] [INFO] OpenEJB :: Server :: Http . SUCCESS [2:26.130s] [INFO] OpenEJB :: Server :: Webservices .. SUCCESS [3.256s] [INFO] OpenEJB :: Server :: CXF Transport SUCCESS [2.051s] [INFO] OpenEJB :: Server :: CXF .. SUCCESS [25.343s] [INFO] OpenEJB :: Server :: REST . SUCCESS [1.614s] [INFO] OpenEJB :: Server :: CXF RS ... SUCCESS [1:04.169s] [INFO] OpenEJB :: Server :: Daemon ... SUCCESS [1.191s] [INFO] OpenEJB :: Assembly ... SUCCESS [0.046s] [INFO] OpenEJB :: Assembly :: Standalone . SUCCESS [18.565s] [INFO] OpenEJB :: iTests :: Failover EJB . SUCCESS [0.389s] [INFO] OpenEJB :: Arquillian Adaptors Parent . SUCCESS [0.043s] [INFO] OpenEJB :: Arquillian Adaptors Parent :: Common ... SUCCESS [3.305s] [INFO] OpenEJB :: TomEE .. SUCCESS [1.008s] [INFO] OpenEJB :: TomEE :: Util .. SUCCESS [1.047s] [INFO] OpenEJB :: Utils .. SUCCESS [0.046s] [INFO] OpenEJB :: Utils :: Provisionning . SUCCESS [7.549s] [INFO] OpenEJB :: Arquillian Adaptors Parent :: TomEE Common SUCCESS [3.878s] [INFO] OpenEJB :: iTests :: Failover . SUCCESS [2:43.317s] [INFO] OpenEJB :: Maven Plugins .. SUCCESS [2.406s] [INFO] OpenEJB :: Maven Plugins :: TomEE Maven Plugin SUCCESS [9.731s] [INFO] OpenEJB :: TomEE :: Common SUCCESS [20.971s] [INFO] OpenEJB :: TomEE :: Loader SUCCESS [1.769s] [INFO] OpenEJB :: TomEE :: JDBC .. SUCCESS [13.652s] [INFO] OpenEJB :: TomEE :: Catalina .. SUCCESS [13.827s] [INFO] OpenEJB :: TomEE :: MyFaces ... SUCCESS [1.820s] [INFO] OpenEJB :: TomEE :: TomEE Embedded SUCCESS [42.839s] [INFO] OpenEJB :: Maven Plugins :: Util .. SUCCESS [1.183s] [INFO] OpenEJB :: Maven Plugins :: TomEE Embedded Maven Plugin SUCCESS [12.611s] [INFO] OpenEJB :: Maven Plugins :: OpenEJB Embedded Maven Plugin SUCCESS [7.797s] [INFO] OpenEJB :: Maven Plugins :: TomEE Webapp Archetype SUCCESS [0.466s] [INFO] OpenEJB :: Maven Plugins :: jars.txt Maven Plugin . SUCCESS [1.184s] [INFO] OpenEJB :: Container :: JUnit . SUCCESS [14.153s] [INFO] OpenEJB :: Server :: ActiveMQ .
Re: failling tests
http://ci.apache.org/builders/tomee-trunk-ubuntu/builds/347 :) *Romain Manni-Bucau* *Twitter: @rmannibucau https://twitter.com/rmannibucau* *Blog: **http://rmannibucau.wordpress.com/*http://rmannibucau.wordpress.com/ *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2013/5/13 Romain Manni-Bucau rmannibu...@gmail.com Hi Andy, great to see :) we basically fixed all the issue on OWB side and TomEE one (one was still here this morning but only visible with profile all-adapters activated) I think we should be good tomorrow (build + TCK) *Romain Manni-Bucau* *Twitter: @rmannibucau https://twitter.com/rmannibucau* *Blog: **http://rmannibucau.wordpress.com/*http://rmannibucau.wordpress.com/ *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2013/5/13 AndyG andy.gumbre...@orprovision.com Just built off trunk, so working for me [INFO] Apache OpenEJB SUCCESS [7.382s] [INFO] OpenEJB :: Dependencies ... SUCCESS [0.201s] [INFO] OpenEJB :: Dependencies :: MBean Annotation API ... SUCCESS [4.583s] [INFO] OpenEJB :: iTests . SUCCESS [0.186s] [INFO] OpenEJB :: iTests :: Beans SUCCESS [6.425s] [INFO] OpenEJB :: iTests :: Servlets . SUCCESS [1.068s] [INFO] OpenEJB :: iTests :: Client ... SUCCESS [10.351s] [INFO] OpenEJB :: iTests :: Interceptor Beans SUCCESS [0.786s] [INFO] OpenEJB :: iTests :: App .. SUCCESS [2.234s] [INFO] OpenEJB :: iTests :: Web .. SUCCESS [1.452s] [INFO] OpenEJB :: Container .. SUCCESS [0.242s] [INFO] OpenEJB :: Container :: Loader SUCCESS [2.233s] [INFO] OpenEJB :: Container :: JPA Integration ... SUCCESS [2.172s] [INFO] OpenEJB :: Container :: API ... SUCCESS [0.745s] [INFO] OpenEJB :: Container :: Java Agent SUCCESS [0.612s] [INFO] OpenEJB :: Container :: Java EE ... SUCCESS [41.398s] [INFO] OpenEJB :: Container :: Java EE Accessors . SUCCESS [9.036s] [INFO] OpenEJB :: Container :: Core .. SUCCESS [12:19.537s] [INFO] OpenEJB :: Server . SUCCESS [0.077s] [INFO] OpenEJB :: Server :: Client ... SUCCESS [8.288s] [INFO] OpenEJB :: Server :: Core . SUCCESS [7.009s] [INFO] OpenEJB :: Server :: Multicast Discovery .. SUCCESS [40.284s] [INFO] OpenEJB :: Server :: EJBd . SUCCESS [1:52.201s] [INFO] OpenEJB :: Server :: Hsql . SUCCESS [1.361s] [INFO] OpenEJB :: Server :: Http . SUCCESS [2:26.130s] [INFO] OpenEJB :: Server :: Webservices .. SUCCESS [3.256s] [INFO] OpenEJB :: Server :: CXF Transport SUCCESS [2.051s] [INFO] OpenEJB :: Server :: CXF .. SUCCESS [25.343s] [INFO] OpenEJB :: Server :: REST . SUCCESS [1.614s] [INFO] OpenEJB :: Server :: CXF RS ... SUCCESS [1:04.169s] [INFO] OpenEJB :: Server :: Daemon ... SUCCESS [1.191s] [INFO] OpenEJB :: Assembly ... SUCCESS [0.046s] [INFO] OpenEJB :: Assembly :: Standalone . SUCCESS [18.565s] [INFO] OpenEJB :: iTests :: Failover EJB . SUCCESS [0.389s] [INFO] OpenEJB :: Arquillian Adaptors Parent . SUCCESS [0.043s] [INFO] OpenEJB :: Arquillian Adaptors Parent :: Common ... SUCCESS [3.305s] [INFO] OpenEJB :: TomEE .. SUCCESS [1.008s] [INFO] OpenEJB :: TomEE :: Util .. SUCCESS [1.047s] [INFO] OpenEJB :: Utils .. SUCCESS [0.046s] [INFO] OpenEJB :: Utils :: Provisionning . SUCCESS [7.549s] [INFO] OpenEJB :: Arquillian Adaptors Parent :: TomEE Common SUCCESS [3.878s] [INFO] OpenEJB :: iTests :: Failover . SUCCESS [2:43.317s] [INFO] OpenEJB :: Maven Plugins .. SUCCESS [2.406s] [INFO] OpenEJB :: Maven Plugins :: TomEE Maven Plugin SUCCESS [9.731s] [INFO] OpenEJB :: TomEE :: Common SUCCESS [20.971s] [INFO] OpenEJB :: TomEE :: Loader SUCCESS [1.769s] [INFO] OpenEJB :: TomEE :: JDBC .. SUCCESS [13.652s] [INFO] OpenEJB :: TomEE :: Catalina .. SUCCESS [13.827s] [INFO] OpenEJB :: TomEE :: MyFaces ... SUCCESS [1.820s] [INFO] OpenEJB :: TomEE :: TomEE Embedded SUCCESS [42.839s] [INFO] OpenEJB :: Maven Plugins :: Util .. SUCCESS [1.183s] [INFO] OpenEJB :: Maven Plugins :: TomEE Embedded
Re: OPENEJB-1306 - EJB's cannot be declared final
Hey guys, did someone already committed David's patch? If not, I can do that. Thanks David anyway. Jean-Louis 2013/4/3 David Salter davidmsal...@me.com I've attacked a patch to JIRA OPENEJB-1306 Validation: EJB's cannot be declared as final - https://issues.apache.org/jira/browse/OPENEJB-1306 In the patch, I've added a class that validates whether EJBs are final and issues a warning upon deployment if they are. I've also included tests for testing @Stateful, @Stateless and @Singleton EJBs are not declared as final. The warning message is defined within the Messages.properties file similar to all the other validation messages. Please let me know if this is OK. Thanks, Dave. On 2 Apr 2013, at 22:46, David Salter davidmsal...@me.com wrote: Yes, the patch I've done gives a warning on deployment but doesn't make it fail. I'll attach a patch to JIRA tomorrow. On 2 Apr 2013, at 22:41, Romain Manni-Bucau rmannibu...@gmail.com wrote: While it generates a warning ok (but dont make deployment fail, would break some apps). Le 2 avr. 2013 23:38, David Salter davidmsal...@me.com a écrit : Yes, I've noticed that the Spec says EJBs cannot be final, but OpenEJB works correctly whether EJBs are final or not. Best to agree with the spec I think though. Dave. On 2 Apr 2013, at 22:12, Romain Manni-Bucau rmannibu...@gmail.com wrote: That s forbidden by the spec but tolerated by most of servers Le 2 avr. 2013 23:07, Mark Struberg strub...@yahoo.de a écrit : here's my take: @Stateless class can only be final (if any) if it has an explicit local interface imo. It must _not_ be final if it only has a No-Interface View. @Stateful must not be final if it has a CDI scope (because in that case CDI proxying rules apply). LieGrue, strub - Original Message - From: Romain Manni-Bucau rmannibu...@gmail.com To: dev@tomee.apache.org Cc: Sent: Tuesday, April 2, 2013 9:02 PM Subject: Re: OPENEJB-1306 - EJB's cannot be declared final Hmm, pby a bad practisebut it should work (at least it works in other app servers) Le 2 avr. 2013 20:08, David Salter davidmsal...@me.com a écrit : Hi, I'm working on a patch for OPENEJB-1306 which I've almost got complete. I just wanted to verify that the issue is that EJB3 beans, i.e. those annotated with @Singleton, @Stateless or @Stateful cannot be declared as final. Thanks, Dave. -- Jean-Louis
Re: OPENEJB-1294
Same here, someone already committed? JLouis 2013/5/10 David Salter davidmsal...@me.com Hi, I've just submitted a patch to JIRA for OPENEJB-1294 that validates classes with the @StatefulTimeout annotation on them. The validation issues a warning if a non @Stateless bean (@Stateful, @Singleton, @ManagedBean, @MessageDriven) has a @StatefulTimeout annotation on it. Hope this is ok. Thanks, Dave. -- Jean-Louis
Re: tomee next classloading
Basically proove me there is any regression introduce by it...noone so no change on the behavior...it just pass when it was not starting Le 13 mai 2013 23:14, Jean-Louis MONTEIRO jeano...@gmail.com a écrit : Let's see what will be the result. It's interesting. But once again, -1 to change the default behavior. Jean-Louis 2013/5/13 Romain Manni-Bucau rmannibu...@gmail.com well IMO we should go for 1 with a config to fallback to what we have now to get a nice default i'll try to commit it to see how TCKs behave with such a config, then we'll see i think *Romain Manni-Bucau* *Twitter: @rmannibucau https://twitter.com/rmannibucau* *Blog: **http://rmannibucau.wordpress.com/* http://rmannibucau.wordpress.com/ *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2013/5/13 David Blevins david.blev...@gmail.com In a similar boat. I think #1 is a feature we need regardless, though I agree with JL that the default should be as it is now. I have a small hope that we could find a way to make managing shaded dependencies a bit easier. If we could find a cleaner way to do it than we do now, might be more realistic to try. It's a bit of a project though. -David On May 13, 2013, at 1:31 PM, Romain Manni-Bucau rmannibu...@gmail.com wrote: i'm playing with 1 ATM, 2 would be the best but we'd need to maintain it...impossible today a shade will not work without custom clever transformer (never a good solution) so basically i'm for 1/ too if my tests show it works fine enough *Romain Manni-Bucau* *Twitter: @rmannibucau https://twitter.com/rmannibucau* *Blog: **http://rmannibucau.wordpress.com/* http://rmannibucau.wordpress.com/ *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2013/5/13 Jean-Louis MONTEIRO jeano...@gmail.com 1/ just adding a property for an app with values like parent-first (default - today) and parent-last (new value). 2/ that usually the way other apps servers are used to do (IBM Websphere AS IIR) 3/Don't know 4/No The first one looks the more simple to implement (at first glance) and the one which produce less impacts and possible side effects for users. The second is something which can be studied furthermore and implement as a cherry on the cake. Then, if I had to choose, I would choose 1/ Jean-Louis 2013/5/13 Romain Manni-Bucau rmannibu...@gmail.com Hi as you probably know we changed quite often the classloading these last versions. We still have regularly issues with tomee provided libs (mainly because of cxf/amq/... transitive deps) I would like to go further and use an URLClassLoaderFirst for lib part of ear to allow apps to not rely on tomee libs first. The alternative is to shade/repackage all deps. PS: i want to avoid OSGi So basically here is the question: to solve conflict lib issue what your preferred solution: 1) URLClassLoaderFirst even for ear lib part - if this one please say if you would like a property to switch back to old behavior (openejb.ear.lib.classloader.first=false?) 2) repackage all deps 3) other 4) OSGi/OSGi like ? If nothing moves in the following days i'll go for 1 (then we can still discuss ;). *Romain Manni-Bucau* *Twitter: @rmannibucau https://twitter.com/rmannibucau* *Blog: **http://rmannibucau.wordpress.com/* http://rmannibucau.wordpress.com/ *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* -- Jean-Louis -- Jean-Louis
Re: tomee next classloading
I don't think I understand this sentence. Can you rephrase? -David On May 13, 2013, at 2:19 PM, Romain Manni-Bucau rmannibu...@gmail.com wrote: Basically proove me there is any regression introduce by it...noone so no change on the behavior...it just pass when it was not starting Le 13 mai 2013 23:14, Jean-Louis MONTEIRO jeano...@gmail.com a écrit : Let's see what will be the result. It's interesting. But once again, -1 to change the default behavior. Jean-Louis 2013/5/13 Romain Manni-Bucau rmannibu...@gmail.com well IMO we should go for 1 with a config to fallback to what we have now to get a nice default i'll try to commit it to see how TCKs behave with such a config, then we'll see i think *Romain Manni-Bucau* *Twitter: @rmannibucau https://twitter.com/rmannibucau* *Blog: **http://rmannibucau.wordpress.com/* http://rmannibucau.wordpress.com/ *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2013/5/13 David Blevins david.blev...@gmail.com In a similar boat. I think #1 is a feature we need regardless, though I agree with JL that the default should be as it is now. I have a small hope that we could find a way to make managing shaded dependencies a bit easier. If we could find a cleaner way to do it than we do now, might be more realistic to try. It's a bit of a project though. -David On May 13, 2013, at 1:31 PM, Romain Manni-Bucau rmannibu...@gmail.com wrote: i'm playing with 1 ATM, 2 would be the best but we'd need to maintain it...impossible today a shade will not work without custom clever transformer (never a good solution) so basically i'm for 1/ too if my tests show it works fine enough *Romain Manni-Bucau* *Twitter: @rmannibucau https://twitter.com/rmannibucau* *Blog: **http://rmannibucau.wordpress.com/* http://rmannibucau.wordpress.com/ *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2013/5/13 Jean-Louis MONTEIRO jeano...@gmail.com 1/ just adding a property for an app with values like parent-first (default - today) and parent-last (new value). 2/ that usually the way other apps servers are used to do (IBM Websphere AS IIR) 3/Don't know 4/No The first one looks the more simple to implement (at first glance) and the one which produce less impacts and possible side effects for users. The second is something which can be studied furthermore and implement as a cherry on the cake. Then, if I had to choose, I would choose 1/ Jean-Louis 2013/5/13 Romain Manni-Bucau rmannibu...@gmail.com Hi as you probably know we changed quite often the classloading these last versions. We still have regularly issues with tomee provided libs (mainly because of cxf/amq/... transitive deps) I would like to go further and use an URLClassLoaderFirst for lib part of ear to allow apps to not rely on tomee libs first. The alternative is to shade/repackage all deps. PS: i want to avoid OSGi So basically here is the question: to solve conflict lib issue what your preferred solution: 1) URLClassLoaderFirst even for ear lib part - if this one please say if you would like a property to switch back to old behavior (openejb.ear.lib.classloader.first=false?) 2) repackage all deps 3) other 4) OSGi/OSGi like ? If nothing moves in the following days i'll go for 1 (then we can still discuss ;). *Romain Manni-Bucau* *Twitter: @rmannibucau https://twitter.com/rmannibucau* *Blog: **http://rmannibucau.wordpress.com/* http://rmannibucau.wordpress.com/ *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* -- Jean-Louis -- Jean-Louis
