Scott M Stark wrote: > That is correct. The packaging required to run under a 2.2 servlet container > is inconsistent with that required to run under a 2.3 container due to the > change in the web container class loader behavior. I see this with Tomcat > 3.2.3 > vs Tomcat 4.0. Really, the only time this shows up is for JSP pages trying > to access EJBs.
Well, *all* access from the web container to EJB's (i.e. servlets too) need to be aware of these changes. We ran into this the other day, and the fix was to bundle crimson.jar into our app too (i.e. not rely on it being available). Now, because of all this bundling going on, the EAR quickly grows HUGE, which means that for development you want hot-deploy on exploded EAR files. Unfortunately JBoss does not currently support that, so the cycling time becomes somewhat excessive. :-( /Rickard -- Rickard Öberg _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
