FileURLConnection breaks if path has spaces
-------------------------------------------

         Key: JBAS-1545
         URL: http://jira.jboss.com/jira/browse/JBAS-1545
     Project: JBoss Application Server
        Type: Bug
    Versions:  JBossAS-4.0.1 SP1    
 Environment: AMD 2600, Windows XP
Java Version "1.4.2_07" 
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_07-b05) 
Java HotSpot(TM) Client VM (build 1.4.2_07-b05, mixed mode) 
    Reporter: Dave Lindquist


The org.jboss.net.protocol.file.FileURLConnection object is unable to handle 
paths with spaces, and seems to die.

For example, when trying to parse an XML document through Xerces, calling the 
method:

DocumentBuilder.parse(File filename)

where "filename" is equal to "D:\path\with spaces\to\file.xml" will produce 
this:

java.io.FileNotFoundException: D:\path\with%20spaces\to\file.xml 
     at 
org.jboss.net.protocol.file.FileURLConnection.connect(FileURLConnection.java:71)
 
     at 
org.jboss.net.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:80)
 
     at org.apache.xerces.impl.XMLEntityManager.setupCurrentEntity(Unknown 
Source) 
     at org.apache.xerces.impl.XMLVersionDetector.determineDocVersion(Unknown 
Source) 
     at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) 
     at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) 
     at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) 
     at org.apache.xerces.parsers.DOMParser.parse(Unknown Source) 
     at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source) 
     at javax.xml.parsers.DocumentBuilder.parse(Unknown Source) 
...etc...

Note that the filename now suddenly has "%20" in it.

The problem persists inspite of setting JAVA_OPTS to 
"-Dorg.jboss.net.protocol.file.decodeFilePaths=true" as recommended in 
"JBAS-363" (yes, the output of "run.bat" was noted, and it did confirm that 
JAVA_OPTS was set).

This is a MAJOR blocker, as it is impossible to parse XML files if their path 
has a space in it, and there appears to be no workaround.

-- 
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
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
JBoss-Development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to