Not going to happen. You have a Pink and the Brain episode running with UnifiedClassLoaders trying to take over the world. Forget about world class loader domination.
----- Original Message ----- From: "marc fleury" <[EMAIL PROTECTED]> To: "Scott M Stark" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Thursday, February 21, 2002 4:39 AM Subject: RE: [JBoss-dev] Why add anything from a war to the JBoss classpath > fuck tomcat > > marcf > > |-----Original Message----- > |From: [EMAIL PROTECTED] > |[mailto:[EMAIL PROTECTED]]On Behalf Of Scott > |M Stark > |Sent: Thursday, February 21, 2002 1:40 AM > |To: [EMAIL PROTECTED] > |Subject: Re: [JBoss-dev] Why add anything from a war to the JBoss > |classpath > | > | > |We don't look into the war at all. Its now an atomic component. > |It was looking into the war and finding jars that caused the > |problems in the first place. If you want to deploy sars or > |common jars you have to use an ear. > | > |Its fine that Jetty can completely delegate all class loading, but Tomcat > |won't allow this. It will delegate to a parent class loader but it will > |continue to create its own class loaders as it sees fit for the war > |contents. And if it first looks to its local WEB-INF/classes and > |WEB-INF/lib before calling our class loaders, and then interacts > |with an EJB that does see some shared classes in a WEB-INF/lib/jar > |we found, I think we will again have class loader conflicts. > | _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
