"Timothy Bennett" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > From: "Stephen McConnell" <[EMAIL PROTECTED]> > > > > Looking at the error message here it appears the the context classloader > > is not being supplied as the parent classloader to the jetty http > > context. I don't know much about jetty but based on a browse though the > > javadocs my guess is that you need to do something like: > > > > // create the web app context (using whatever approach your > > // currently using - the following is only illustrative) > > > > WebApplicationContext context = new WebApplicationContext(); > > > > // this is the important bit > > // set the parent classloader using the classloader merlin > > // has assigned to the container thread > > > > context.setParentClassLoader( > > Thread.currentThread().getContextClassLoader() ); > > > > This should ensure that the classloader assigned to the container is > > established as the parent classloader for the jetty HTTPContext. > > > > Sounds right on the money. I'll give it a whirl, and post back my results.
Actually turned out to be a funky and complex classloading strategy that Jetty passes to webapps. Basically ignores any classloaders and only looked at what was in the system CLASSPATH definition. After some lengthy discussions with Greg over at mortbay, I got it working with some pre-release code from him. Jetty 4.2.14 is due out imminently that improves the creation of the classpath that gets passed to webapps. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
