[
https://issues.apache.org/jira/browse/XMLCOMMONS-71?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Glavassevich updated XMLCOMMONS-71:
-------------------------------------------
Fix Version/s: XML Commons Resolver 1.2.0
> Behaviour for null/default namespace unspecified; NPE's for null publicId.
> --------------------------------------------------------------------------
>
> Key: XMLCOMMONS-71
> URL: https://issues.apache.org/jira/browse/XMLCOMMONS-71
> Project: XmlCommons
> Issue Type: Bug
> Components: XML Commons Resolver (resolver.jar)
> Affects Versions: 1.x
> Environment: Operating System: Linux
> Platform: PC
> Reporter: Chris Simmons
> Assignee: Commons Developers Mailing List
> Fix For: XML Commons Resolver 1.2.0
>
> Attachments: TestResolveDefaultNamespace.java
>
>
> Created an attachment (id=23777)
> Test case showing the NPE.
> When using the resolvePublic method for a schema with the null namespace, or
> an attribute in the default namespace, this method is likely to be called.
> DOM uses 'null' for this namespace whereas JAXP tends to use the empty string
> (see javax.xml.XMLConstants.NULL_NS_URI) so the javadoc should specify which
> is used in the resolver internals.
> The code has lots of null checks in this method which makes me think you
> expect null to be passed in and yet this null pointers as seen in the
> attached test case.
> I can't vouch for whether or not the resolver behaves sensibly when the
> publicId is empty string.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
