Hi, ok, that's not so good, but well...
But can I configure this on Tomcat 4.1.x ??? There exists a lot of different ClassLoaders, but we haven't tested Tomcat 4 yet! Are there some options to allow our Application-Monitor to access Classes from different Contexts? Thanx, Stefan ----- Original Message ----- From: "Craig R. McClanahan" <[EMAIL PROTECTED]> To: "Tomcat Users List" <[EMAIL PROTECTED]> Sent: Monday, July 08, 2002 12:07 AM Subject: Re: Accessing Classes from different Context > > > On Sun, 7 Jul 2002 [EMAIL PROTECTED] wrote: > > > Date: Sun, 7 Jul 2002 15:13:25 +0200 > > From: [EMAIL PROTECTED] > > Reply-To: Tomcat Users List <[EMAIL PROTECTED]> > > To: [EMAIL PROTECTED] > > Subject: Accessing Classes from different Context > > > > Hi, > > > > we just wrote an Application-Monitor. It just works fine, but he cannot > > access Classes from different Contexts under Tomcat 3.2.4 > > cross-context and trustable are set both to true > > What must we configure, that our Application-Monitor can access to the > > Classes that lay unter WEB-INF from other Contexts? > > > > Classes loaded from a different webapp's classloader are never shared. In > order to be able to share them, the relevant classes need to be loaded by > the same classloader -- for Tomcat 3.2.x (which, by the way, is really > ancient history), that means putting them on the system CLASSPATH. > > > Thanx, > > > > Stefan Hadasch > > > > Craig > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
