----- Original Message ----- From: "Jeremy Boynes" <[EMAIL PROTECTED]> To: "Jboss-Development" <[EMAIL PROTECTED]> Sent: Thursday, December 19, 2002 9:50 AM Subject: [JBoss-dev] Committed support for remote deployment scanning
> * All WARs must contain all jars needed for JSP compilation. The Jasper > compiler needs the compilation classpath supplied as a String of > concatenated local paths and any http: based URLs are excluded. This means > anything added to the classpath during boot is not available if the > server was netbooted. This should not be an issue for normal applications > but was for jmx-console.war which assumed jboss-jmx.jar would be on the > compilation classpath. This is a big problem and something we have worked to avoid with our 3.0 classloading model. Explain why the boot classpath is not available. xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx ------------------------------------------------------- This SF.NET email is sponsored by: Geek Gift Procrastinating? Get the perfect geek gift now! Before the Holidays pass you by. T H I N K G E E K . C O M http://www.thinkgeek.com/sf/ _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
