I have commited changes to URLDeploymentScanner that use WebDAV to scan http: locations, allowing the same config to be booted locally or via netboot.
There are a couple of changes that may impact existing configurations: * It needs to know whether to scan or deploy a supplied URL. It does this by seeing if the URL ends in a "/" (as it should do for a directory) rather than by doing an extra network trip. So "./deploy" became "deploy/" I updated the default jboss-service.xml but modified versions will be impacted. * All remote deployables must be packed. This seemed reasonable as you would want to fetch them in one operation rather than recursing down the remote collection hierarchy (which would be rather inefficient). * 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 change incorporates all the functionality in URLDirectoryScanner and HttpDeploymentScanner - are people using these or can I delete them? Finally, I tested this on a single node but FarmServiceMember extends URLDeploymentScanner so cluster configs may be affected. Can someone give me guidelines on running the cluster testsuite (e.g. what config/hardware do I need), or quickly test this for me? Cheers Jeremy ------------------------------------------------------- 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
