| <mbean code="org.jboss.deployment.scanner.URLDeploymentScanner" | name="jboss.deployment:type=DeploymentScanner,flavor=URL"> | | <!-- Uncomment (and comment/remove version below) to enable usage of |the DeploymentCache | <depends |optional-attribute-name="Deployer">jboss.deployment:type=Deployment |Cache</depends> | --> | <depends |optional-attribute-name="Deployer">jboss.system:service=MainDeploye |r</depends> | | <attribute name="ScanPeriod">5000</attribute> | | <!-- | | URLs are comma seperated and unprefixed arguments are considered | | file URLs and resolve relative to server home unless the given |path | | is absolute. | --> | <attribute name="URLs"> | ./deploy/jar1.jar, | ./deploy/sar2.sar, | ./deploy/war3.war, | ./deploy/jar4.jar, | ./deploy | </attribute> | </mbean> | |Which is easier, setting it one place here or changing n names in your m |ant build scripts, scattered all over your hard drive? Suppose you want to |change the order? Would you rather go to one config file or your nXm |places in ant scripts? Please explain how distributing the deployment |order over so many places is easier to use than concentrating it in one |place.
What are you talking about? CLEARLY say 01jar1.jar 02sar2.jar 03war3.war 04jar4.jar in a directory is CLEARLY SIMPLER end of story marcf _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
