[jboss-jira] [JBoss JIRA] Closed: (JBAS-1714) -service.xml not deploying deploy/*.jar correctly

-service.xml not deploying deploy/*.jar correctly ------------------------------------------------- Key: JBAS-1714 URL: http://jira.jboss.com/jira/browse/JBAS-1714 Project: JBoss Application Server Issue Type: Bug Security Level: Public(Everyone can see) Components: Deployment services Reporter: SourceForge User SourceForge Submitter: ioparra . Refer to my previous postings in the forums: http://www.jboss.org/thread.jsp? forum=63&thread=36306 The SAR Deployer is locking down jars in the deploy directory instead of deploying those jars correctly. This event occurs when you have a "classpath" entry in your mbean. If that classpath has a codebase="."(ie, its codebase is the deploy directory), this SAR Deployer adds this jar to UCL repository. Issues: 1)the url for this jar points to the deploy directory(not a temp directory) a. when the service is run, this jar is no longer deleteable(on windows, dunno about unix). 2)The DirectoryScanner picks up this jar while scan. The scanner copies/deploys the jar from the tmp directory, leading to a new/managed UCL. The UCLRepository doesn't know its a duplicate becuase it compares the URLs(one url is from deploy, the other from tmp). Possible work-around/solution: The SAR deployer already does a check if the classpath="."(ie, the deploy directory). If true, call mainDeployer.deploy(url) and don't call addURL. I don't know the full implications of making this change. If I have time, I'll try it out and post a patch.