[
https://issues.apache.org/jira/browse/XALANC-754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13800945#comment-13800945
]
Kelly Graus commented on XALANC-754:
------------------------------------
Looking into this further, my workaround only partially worked due to the fact
I had implemented a custom EntityResolver that could deal with malformed URLs.
However, there are still several problems related to Xerces throwing
MalformedURLExceptions whenever it encounters these URLs.
I was able to implement a fix in Xalan, but am unsure how to go about
committing it (or if it's even "worthy" to be committed, I have by no means
done more than cursory testing on it). I will attach the two files that I
changed.
> Crash parsing windows file url
> ------------------------------
>
> Key: XALANC-754
> URL: https://issues.apache.org/jira/browse/XALANC-754
> Project: XalanC
> Issue Type: Bug
> Components: XalanC
> Affects Versions: 1.11
> Environment: Windows, Visual Studio 2010
> Reporter: Kelly Graus
> Assignee: Steven J. Hathaway
> Attachments: XalanDOMString.hpp, XalanParsedURI.cpp
>
>
> When parsing a windows file URL (file:///c:/somefile), the XalanParsedURL
> class crashes when parsing the authority.
> Removing one of the slashes after "file" works around the crash and allows
> the correct file to be accessed, but it's not a valid URL.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
