Hi Anatoly, I just found your e-mail from ages ago in my mailbox ... what a shame :-(
The J2eeScopeDeployer is a prototype that worked just at the level of ear�s and should enlighten the concept of alternative classloading. The current RH-sar-ServiceDeployer is derived from that code, but works at another level of classloading (the former Mbean level). If you look at the current efforts, I think that it is now tried to unify the sar classloader stuff with the rest of the deployer code, maybe by having scoped deployment features in DeploymentMBeanSupport ... The tomcat/jetty problem (or better: the f***cked compiler problem) is tried to solve by Jules currently by (re-)collecting the jar locations from the classloaders ... Not very nice, but another stance of "work around big company, but small brain output". CGJ -----Urspr�ngliche Nachricht----- Von: Anatoly Akkerman [mailto:[EMAIL PROTECTED]] Gesendet: Mittwoch, 7. November 2001 23:52 An: JBoss-Dev Betreff: [JBoss-dev] Question about Scoped Deployer Hi, First and foremost, thank you, Dr. Jung. I was wondering if scoped deployment is capable of handling the WAR archives as well (stored in an EAR of their own). From my initial tests and without looking at the code (being lazy :) it seems that Tomcat cannot load classes from the common Scope class loader (at least when compiling JSPs ?) Perhaps it has to do with how it compiles the JSPs, i.e. the compiler only looks into its classpath (perhaps setup by Tomcat to include the WEB-INF/classes directory plus the standard jars) and does not use the classloader to obtain the classes. Could this be the culprit? Thank you. Anatoly Akkerman. _______________________________________________ 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
