if you deploy the nukes-downloads.ear first, and then deploy the individual -service.xml files, it should startup w/o any issues.
the problem is the -service.xml files and the nukes-downloads.ear are both in the "nukes" directory, and the -service.xml file is being deployed before the .ear. a few solutions comes to mind... 1) roll the individual -service.xml files back into the main jboss-service.xml file that is contained in the ear (packaged in the sar). 2) since the URLComparator deploys anything not matching the already specified criteria last, the -service.xml files could be renamed to have a special suffix (or prefix) and then a custom deployer (which would be nothing more then an extension of the SARDeployer) could then be used to deploy the files. 3) have a "nukes.last" directory that all the -service.xml files are deployed to so they are deployed last. personally, i like #2 the best. in the interim, i will implement solution #1 and investigate #2 in more depth. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3837275#3837275 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3837275 ------------------------------------------------------- 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
