[Jetty-support] Space in path problem with jboss-3.2.3RC1-jetty-4.2.14

SourceForge Headquarters 1320 Columbia Street Suite 310 San Diego, CA 92101 +1 (858) 422-6466

Hi,
I'm upgrading to jboss-3.2.3RC1-jetty-4.2.14 (from
jboss-3.2.2RC3_jetty-4.2.11) and hit a problem when deploying war files. I
skimmed the last few weeks of posts but couldn't find anything related to
this. When deploying a war file I get the following exception (the example
is for the JMX-console):

16:40:23,937 INFO [jetty] Registered
jboss.jetty:Server=0,JBossWebApplicationContext=0,context=/jmx-console
16:43:08,468 INFO [jetty] Checking Resource aliases
16:47:24,171 WARN [jetty] WARNING: Configuration error on file:/D:/Program
Files/Tumbleweed/MMS/Messenger/server/default/deploy/jmx-console.war/
java.io.FileNotFoundException:
D:\Program%20Files\Tumbleweed\MMS\Messenger\server\default\deploy\jmx-consol
e.war\WEB-INF\web.xml
at
org.jboss.net.protocol.file.FileURLConnection.connect(FileURLConnection.java
:70)
at
org.jboss.net.protocol.file.FileURLConnection.getInputStream(FileURLConnecti
on.java:79)
at java.net.URL.openStream(URL.java:913)
at
org.apache.xerces.impl.XMLEntityManager.startEntity(XMLEntityManager.java:74
0)
at
org.apache.xerces.impl.XMLEntityManager.startDocumentEntity(XMLEntityManager
.java:685)
at
org.apache.xerces.impl.XMLDocumentScannerImpl.setInputSource(XMLDocumentScan
nerImpl.java:252)
at
org.apache.xerces.parsers.StandardParserConfiguration.parse(StandardParserCo
nfiguration.java:503)
at
org.apache.xerces.parsers.StandardParserConfiguration.parse(StandardParserCo
nfiguration.java:585)
at org.apache.xerces.parsers.XMLParser.parse(XMLParser.java:147)
at
org.apache.xerces.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:114
8)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:345)
at org.mortbay.xml.XmlParser.parse(XmlParser.java:123)
at org.mortbay.xml.XmlParser.parse(XmlParser.java:138)
at
org.mortbay.jetty.servlet.WebApplicationContext.start(WebApplicationContext.
java:394)
at
org.mortbay.j2ee.J2EEWebApplicationContext.start(J2EEWebApplicationContext.j
ava:85)
at
org.jboss.jetty.JBossWebApplicationContext.start(JBossWebApplicationContext.
java:88)
at org.jboss.jetty.Jetty.deploy(Jetty.java:327)
at org.jboss.jetty.JettyService.performDeploy(JettyService.java:242)
at org.jboss.web.AbstractWebContainer.start(AbstractWebContainer.java:428)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:832)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:642)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:605)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39
)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at
org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispat
cher.java:284)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:546)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
at $Proxy6.deploy(Unknown Source)
at
org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanne
r.java:302)
at
org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.
java:476)
at
org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(
AbstractDeploymentScanner.java:201)
at
org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(Abstract
DeploymentScanner.java:274)
at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:192)
at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at
org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispat
cher.java:284)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:546)
at
org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.jav
a:976)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:394)
at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at
org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispat
cher.java:284)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:546)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
at $Proxy4.start(Unknown Source)
at org.jboss.deployment.SARDeployer.start(SARDeployer.java:226)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:832)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:642)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:605)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:589)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39
)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at
org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispat
cher.java:284)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:546)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
at $Proxy5.deploy(Unknown Source)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:384)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:291)
at org.jboss.Main.boot(Main.java:150)
at org.jboss.Main$1.run(Main.java:395)
at java.lang.Thread.run(Thread.java:534)

The problem is that the path contains a space "D:\Program Files", the space
is getting converted to %20 and it appears to be causing the problem. If I
change the path name to "D:\Program_Files" everything deploys fine. I did
some digging around and the problem seems to be in
WebApplicationContext::resolveWebApp(), when it appends the "WEB-INF" it
also replaces the %20. Anyone seen this before? Is it some config problem?
Is there any way to deploy a war file which resides under a directory
containing a space?

Btw I tested it with jetty4.2.15RC0 also and got the same behaviour, however
4.2.11 seems to work fine.

thanks,
gavin