I made what I thought was a small modification to the conf/jboss-service.xml file to add in another deploy directory. The intention was to create a directory in Linux that allowed another group to deploy their applications without having to have permissions to the main deploy directory.
| <mbean code="org.jboss.deployment.scanner.URLDeploymentScanner" | name="jboss.deployment:type=DeploymentScanner,flavor=URL"> | <depends optional-attribute-name="Deployer">jboss.system:service=MainDeployer</depends> | | <attribute name="URLComparator">org.jboss.deployment.DeploymentSorter</attribute> | <attribute name="Filter">org.jboss.deployment.scanner.DeploymentFilter</attribute> | | <attribute name="ScanPeriod">15000</attribute> | | <attribute name="URLs"> | deploy/,othergroupdeploy/ | </attribute> | </mbean> | Unfortunately, whenever one of the files in their deploy directory (othergroupdeploy/) gets updated, ALL the files get redeployed. Anyone have any idea what this might be happening and how to fix it? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3839568#3839568 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3839568 ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
