[ 
https://issues.apache.org/jira/browse/XERCESC-1865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kristian Ivarsson updated XERCESC-1865:
---------------------------------------


... or skip the XMLUni::fgXercesSchema-parameter since there is no 
XMLUni::fgXercesDTD 'cause there are too many parameters anyway :-)

> IGXMLScanner does not recognize XML Schema
> ------------------------------------------
>
>                 Key: XERCESC-1865
>                 URL: https://issues.apache.org/jira/browse/XERCESC-1865
>             Project: Xerces-C++
>          Issue Type: Improvement
>          Components: DOM
>    Affects Versions: 3.0.1
>         Environment: xerces-c-3.0.1-x86-windows-vc-8.0
>            Reporter: Kristian Ivarsson
>
> This might be a documentation-defect (as well)
> Setup:
> ...
> DOMLSParser::getDomConfig::setParameter( xercesc::XMLUni::fgDOMValidate, true 
> ); 
> DOMLSParser::getDomConfig::setParameter( 
> xercesc::XMLUni::fgXercesScannerName, xercesc::XMLUni::fgIGXMLScanner );
> ...
> Parse an XML that referes to an XMLSchema and the parser reports error. By 
> using the SGXMLScanner it works fine and it validates the document correctly 
> but not with IGXMLScanner despite that the documentation says "both XMLSchema 
> and DTD validation".
> In some business-patterns you may just wanna perform "automatic" validation 
> depending on referred/supplied validation-technique in any incoming XML where 
> you do not know what kind of technique the XML refers to i.e. you just wanna 
> validate the XML and therefore you wanna use the something like the 
> IGXMLScanner that, according to the documentation, seems to provide that 
> service ... but it doesn't or something (supplementary) is missing in the 
> documentation 

-- 
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]

Reply via email to