after a quick test, #3 is actually the quickest way to handle this for right now.
in the "nukes" directory (under server/default/), create a directory called "nukes.last" and then copy all the -service.xml files that are contained in the "nukes" directory there. that will eliminate the startup exceptions that are thrown b/c the classes can't be found. for now, i think that will be the best solution and i'll update the build scripts to deploy -service.xml files there instead of worrying about the deployment scanner. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3837285#3837285 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3837285 ------------------------------------------------------- This SF.Net email is sponsored by the new InstallShield X. >From Windows to Linux, servers to mobile, InstallShield X is the one installation-authoring solution that does it all. Learn more and evaluate today! http://www.installshield.com/Dev2Dev/0504 _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
