Scott/Marc, When the Jetty context class loader delegates to it's parent class loader, it expects the parent to throw a ClassNotFoundException if it can't load the class, in which case it then loads it itself. It appears that the quickest fix is for Jetty to catch both exceptions from the parent, but this begs the question as to why the JBoss loader is now exhibiting different behaviour (and if the JBoss loader isn't cracking open the war, then why should it think it is able to get as far as defineClass()????)
Jan >scott, > >I am going to look at this and try and re-establish this behavior (we parse >the files).. > >we can support 2.3 behavior. Straigh Class.forName is a bug. In this case >the previous code would have worked. > >marcf > >|-----Original Message----- >|From: [EMAIL PROTECTED] >|[mailto:[EMAIL PROTECTED]]On Behalf Of Scott >|M Stark >|Sent: Tuesday, February 26, 2002 4:22 PM >|To: [EMAIL PROTECTED] >|Subject: Re: [JBoss-dev] More Ear crap .. >| >| >|The org.mortbay.http.ContextLoader.loadClass should be >|handling jars in WEB-INF/lib. The stack trace is for the >|org.mortbay.http.ContextLoader calling its parent class loader >|which will not have any knowledge of the WEB-INF/lib jars. >|The current jbosstest-web.ear includes jars in WEB-INF/lib >|and these are picked up correctly. Servlets are loaded from >|WEB-INF/classes so a test of loading servlets from a WEB-INF/lib >|jar needs to be added. >| >|xxxxxxxxxxxxxxxxxxxxxxxx >|Scott Stark >|Chief Technology Officer >|JBoss Group, LLC >|xxxxxxxxxxxxxxxxxxxxxxxx >|----- Original Message ----- >|From: "marc fleury" <[EMAIL PROTECTED]> >|To: "Dave Smith" <[EMAIL PROTECTED]>; >|<[EMAIL PROTECTED]> >|Sent: Tuesday, February 26, 2002 6:32 PM >|Subject: RE: [JBoss-dev] More Ear crap .. >| >| >|> take it out of webinf >|> >|> marcf >|> >|> |-----Original Message----- >|> |From: [EMAIL PROTECTED] >|> |[mailto:[EMAIL PROTECTED]]On Behalf Of Dave >|> |Smith >|> |Sent: Tuesday, February 26, 2002 3:13 PM >|> |To: [EMAIL PROTECTED] >|> |Subject: [JBoss-dev] More Ear crap .. >|> | >|> | >|> |Ok what is the currennt status of the ear deployment in the latest head? >|> |I am using a hacked version of cactus where I replaced Class.forName() >|> |with Thread.currentThread.getContextClassLoader().loadClass(). My ear >|> |looks like >|> | >| >| >| >|_______________________________________________ >|Jboss-development mailing list >|[EMAIL PROTECTED] >|https://lists.sourceforge.net/lists/listinfo/jboss-development > > >_______________________________________________ >Jboss-development mailing list >[EMAIL PROTECTED] >https://lists.sourceforge.net/lists/listinfo/jboss-development > _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
