let say we have an interface Foo. I deploy a war with Foo and FooImpl. In the since I'm in embedded mode I can get FooImpl casting it to Foo. Foo has been loaded from the Junit JVM for instance and FooImpl from the webapp cause we use a framework (spring, CDI, ...). The cast will fail cause FooImpl will use Foo from the webapp.
It was working fine before and it was convenient. By default you don't add jars in tomcat system loader so the behavior of tomcat was fine + in unit test of embedded mode it was convenient so I dont get the point changing it. Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2014-02-18 11:11 GMT+01:00 Mark Thomas <ma...@apache.org>: > On 18/02/2014 10:07, Romain Manni-Bucau wrote: >> 2014-02-18 11:04 GMT+01:00 Mark Thomas <ma...@apache.org>: >>> On 18/02/2014 09:59, Romain Manni-Bucau wrote: > > <snip/> > >>>> it doesn't cover the embedded case at all >>> >>> What doesn't? Why? >> >> In embedded case you deploy an app with your classes in the JVM and >> want 1/2 of times to cast both, this was working fine before because >> tomcat was preventing system loader overriding, it is broken now now >> since tomcat only uses ext classloader. > > I have no idea what you mean by "cast both" so I can't follow the point > you are making here at all. > > Mark > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > For additional commands, e-mail: dev-h...@tomcat.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
