You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ws.apache.org by "Daniel Kulp (JIRA)" <ji...@apache.org> on 2014/01/21 19:04:23 UTC
[jira] [Updated] (XMLSCHEMA-3) DefaultURIResolver doesn't resolve
JAR style URLs properly
[ https://issues.apache.org/jira/browse/XMLSCHEMA-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Kulp updated XMLSCHEMA-3:
--------------------------------
Fix Version/s: (was: 2.1.0)
XmlSchema 2.0.1
> DefaultURIResolver doesn't resolve JAR style URLs properly
> ----------------------------------------------------------
>
> Key: XMLSCHEMA-3
> URL: https://issues.apache.org/jira/browse/XMLSCHEMA-3
> Project: XmlSchema
> Issue Type: Bug
> Affects Versions: XmlSchema 1.4.2, XmlSchema 1.4.6
> Reporter: Andreas Veithen
> Priority: Minor
> Fix For: XmlSchema 2.0.1, XmlSchema 1.4.8
>
>
> DefaultURIResolver is unable to resolve entities against a base URI of the following form:
> jar:file:/D:/data/my.jar!/package/schema.xsd
> The reason is that resolveEntity uses java.net.URI: the URI is opaque and java.net.URI doesn't resolve relative URIs against opaque URIs. The original version of DefaultURIResolver (r396478) used java.net.URL and worked perfectly in that case. This was broken in r400374.
> The impact of this issue is that it is not possible to load schemas from the classpath, if they have imports and DefaultURIResolver is used.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ws.apache.org
For additional commands, e-mail: dev-help@ws.apache.org