[ http://jira.jboss.com/jira/browse/JBESB-1336?page=comments#action_12387598 ] Tom Fennelly commented on JBESB-1336: ------------------------------------- Current status... Trying to sort out a new deployment issue. org.jboss.wsf.container.jboss42.WebXMLRewriterImpl added code re JBWS-1762. This code attempts to rename the web.xml in the webservice war deployment. In the case where the .war is bundled inside the .esb, it's running into trouble when attempting to do perform the rename because the file is locked. An exception occurs (from line 91 of WebXMLRewriterImpl). After stepping through the code, it appears as though the TomcatDeployer got in beforehand, deployed the .war and it (??) now has a handle on the file. I'm quite sure this has something to do with the ESB's JBoss4ESBDeployer and the fact that it extends SubDeployerSupport. Haven't got any further on this yet. I'm actually going to work around this for now by deploying the .war outside the .esb (I think this will work). I want to get to the integration issues identified in SOA-102 and see what's involved there before spending too much time on this. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBESB-1336?page=all ] Tom Fennelly closed JBESB-1336. ------------------------------- Resolution: Done done -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira