DO NOT REPLY [Bug 14876] New: - Validation: Why can't the schemaLocation be pulled from the xml document?

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14876>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14876

Validation: Why can't the schemaLocation be pulled from the xml document?

           Summary: Validation: Why can't the schemaLocation be pulled from
                    the xml document?
           Product: Xerces2-J
           Version: 2.2.0
          Platform: PC
        OS/Version: Windows NT/2K
            Status: NEW
          Severity: Major
          Priority: Other
         Component: JAXP
        AssignedTo: xerces-j-dev@xml.apache.org
        ReportedBy: edgar.valenzuela@contentguard.com


I've been reviewing the DOMEcho example provided in JAXP (inside the 
java_xml_pack-summer-02_01 download from sun) and it is not clear to me 
why we have to set the schemaSource on the DocumentBuilderFactory.  I feel that 
if the schemaSource is set to null (or not set at all), the DocumentBuilder(s)
that are created from that factory should take into account the schemaLocation 
from inside of the xml document.  By ignoring the schemaLocation declarations 
within an xml document, Xerces will not be able to handle localized namespace 
declarations and the use of multiple independent schemas by one document.

It is also not convenient to have to go into an xml document to extract the 
schemaLocation so that we can set the schemaSource before we try 
parsing/validating the document.  This means we need to parse twice whenever we 
want to validate.  

I know that the Xerces2-J parser does provide a Parser class that can do this.  
I can see it in the Dom.Count example.  Why can't we integrate that same 
behavior under the JAXP APIs?

Please feel free to contact me for any clarifications. 
Thanks.

---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org