If a web app context has a WEB-INF/classes or non-empty WEB-INF/lib, then we create a mortbay class loader as the thread context class loader. Otherwise, we use the parent class loader as the thread context class loader, which in the case of JBoss will be an MBeanClassLoader.
Jan Jason Dillon wrote: > I don't understand how this is the cause of the ClassCastException? > > Can you explain that please. > > --jason > > > Jan Bartel wrote: > >> Jason, >> >> Okay, I'm not perplexed anymore! :-) Jetty expects to find at least >> either a WEB-INF/classes directory, or a WEB-INF/lib (with at least one >> jar in it) in the webapp directory - so the short term fix is for you >> to create an empty WEB-INF/classes directory, and all should be well. >> >> In the slightly longer term, the fix is for us to deal with non-existant >> WEB-INF directories in a slightly more flexible manner. ;-) >> >> [snip] _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
