[jbossws-issues] [JBoss JIRA] Created: (JBWS-1940) Cannot rename web.xml to web.xml.ejb.org

[Carsten Wolters (JIRA)]

Cannot rename web.xml to web.xml.ejb.org
----------------------------------------

                 Key: JBWS-1940
                 URL: http://jira.jboss.com/jira/browse/JBWS-1940
             Project: JBoss Web Services
          Issue Type: Bug
      Security Level: Public (Everyone can see)
    Affects Versions:  jbossws-2.0.2
         Environment: WindowsXP
            Reporter: Carsten Wolters
            Priority: Blocker


I cannot deploy a webservice and subsequent, the complete ear is not deployed.

The exception I get is:

14:42:51,859 ERROR [org.jboss.deployment.MainDeployer] Could not start deployment: file:/E:/Projekte/pvs/jboss/server/wsdeploy/ws.ear/ws-server.jar/
org.jboss.wsf.spi.deployment.WSFDeploymentException: javax.xml.ws.WebServiceException: Cannot rename web.xml: E:\Projekte\pvs\jboss\server\bardtke\tmp\deploy\ws.ear-ws-server.jar49792.war\WEB-INF\web.xml.ejb.org
	at org.jboss.wsf.spi.deployment.WSFDeploymentException.rethrow(WSFDeploymentException.java:54)
	at org.jboss.wsf.container.jboss40.WebAppDeploymentAspect.create(WebAppDeploymentAspect.java:82)
	at org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl.deploy(DeploymentAspectManagerImpl.java:115)
	at org.jboss.wsf.container.jboss40.ArchiveDeployerHook.deploy(ArchiveDeployerHook.java:97)
	at org.jboss.wsf.container.jboss40.DeployerInterceptor.start(DeployerInterceptor.java:90)
	at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.start(SubDeployerInterceptorSupport.java:188)
	at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:95)
	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
	at $Proxy36.start(Unknown Source)
	at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
	at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1015)
	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
	at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
	at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
	at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
	at $Proxy6.deploy(Unknown Source)
	at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
	at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
	at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
Caused by: javax.xml.ws.WebServiceException: Cannot rename web.xml: E:\Projekte\pvs\jboss\server\bardtke\tmp\deploy\maxtrading.ear-maxtrading-server.jar49792.war\WEB-INF\web.xml.ejb.org
	at org.jboss.wsf.container.jboss40.WebXMLRewriterImpl.rewriteWebXml(WebXMLRewriterImpl.java:91)
	at org.jboss.wsf.container.jboss40.WebAppDeploymentAspect.create(WebAppDeploymentAspect.java:69)
	... 30 more


-----------------------

I found a description of the same problem with a solution here:

http://lists.jboss.org/pipermail/jbossws-dev/2007-November/001075.html

The problem seems to be connected to a deployment on windows filesystems.

-- 
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