xml-commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 47334] New: Behaviour for null/default namespace unspecified; NPE's for null publicId.
Date Tue, 09 Jun 2009 10:44:41 GMT
https://issues.apache.org/bugzilla/show_bug.cgi?id=47334

           Summary: Behaviour for null/default namespace unspecified;
                    NPE's for null publicId.
           Product: XmlCommons
           Version: 1.x
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Resolver
        AssignedTo: commons-dev@xml.apache.org
        ReportedBy: cps@decisionsoft.com


Created an attachment (id=23777)
 --> (https://issues.apache.org/bugzilla/attachment.cgi?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.

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

Mime
View raw message