[jboss-jira] [JBoss JIRA] Closed: (JBAS-3775) org.jboss.net.protocol.file.FileURLConnection does not handle opening InputStreams to UNC paths properly
Dimitris Andreadis (JIRA)
jira-events at lists.jboss.org
Sun Jun 8 18:03:49 EDT 2008
[ http://jira.jboss.com/jira/browse/JBAS-3775?page=all ]
Dimitris Andreadis closed JBAS-3775.
------------------------------------
Fix Version/s: JBossAS-5.0.0.CR1
Resolution: Done
Assignee: Dimitris Andreadis
This shouldn't be an issue anymore as the org.jboss.net.protocol.file.FileURLConnection was dropped, see JBCOMMON-55
> org.jboss.net.protocol.file.FileURLConnection does not handle opening InputStreams to UNC paths properly
> --------------------------------------------------------------------------------------------------------
>
> Key: JBAS-3775
> URL: http://jira.jboss.com/jira/browse/JBAS-3775
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Other
> Affects Versions: JBossAS-4.0.2 Final
> Environment: Microsoft Windows XP [Version 5.1.2600]
> java version "1.5.0_07"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_07-b03)
> Java HotSpot(TM) Client VM (build 1.5.0_07-b03, mixed mode)
> Xerces-J 2.6.2
> Reporter: David Kilzer
> Assigned To: Dimitris Andreadis
> Fix For: JBossAS-5.0.0.CR1
>
>
> Attempting to parse a document using Xerces-J 2.6.2 by passing in a java.io.File object containing a UNC path fails when run under JBossAS 4.0.2 Final, but works fine when run outside of JBoss. The particular code run under JBoss was started through a Spring-1.2.8-controlled Quartz-1.4.5 job (all deployed within a WAR within an EAR), but the stack trace clearly shows that org.jboss.net.protocol.file.FileURLConnection is the culprit (file path changed to protect the innocent):
> java.io.FileNotFoundException: \c$\path\to\file.xml
> at org.jboss.net.protocol.file.FileURLConnection.connect(FileURLConnection.java:80)
> at org.jboss.net.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:89)
> at java.net.URL.openStream(URL.java:1007)
> 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.DTDConfiguration.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(DocumentBuilder.java:172)
> [...]
> Here is some sample code that should reproduce the issue. Note the path used to create the java.io.File object.
> File xmlFile = new File("\\\\127.0.0.1\\c$\\path\\to\\file.xml"):
> DocumentBuilderFactory factory = new org.apache.xerces.jaxp.DocumentBuilderFactoryImpl();
> factory.setNamespaceAware(false);
> factory.setValidating(false);
> DocumentBuilder builder = factory.newDocumentBuilder();
> Document document = builder.parse(xmlFile); // exception thrown under JBossAS
> The FileURLConnection class is loaded from jboss-4.0.2/client/jboss-common-client.jar.
--
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
More information about the jboss-jira
mailing list