[
https://issues.apache.org/jira/browse/XERCESC-1862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16082809#comment-16082809
]
Scott Cantor commented on XERCESC-1862:
---------------------------------------
I suspect documentation, but the weirdness is due to the fact that these
properties actually manipulate that weird validation switch that has the
Auto/Always/Never values and when you fetch them back, they actually depend
only on *that* property's values.
> validate-if-schema and validate are not mutually exclusive
> ----------------------------------------------------------
>
> Key: XERCESC-1862
> URL: https://issues.apache.org/jira/browse/XERCESC-1862
> Project: Xerces-C++
> Issue Type: Bug
> Components: Documentation
> Affects Versions: 3.0.1
> Environment: Windows XP
> Reporter: Kristian Ivarsson
> Priority: Minor
>
> The documentation for DOMConfiguration obtained using
> DOMLSParser::getDomConfig() says "validate-if-schema and validate are
> mutually exclusive, setting one of them to true will set the other one to
> false." and that doesn't seem to be the case at least not when retrieving
> them respectively
> Setting fgDOMValidateIfSchema to true will make getting fgDOMValidate to
> return true as well and setting fgDOMValidate to false will make getting
> fgDOMValidateIfSchema to return false
> Documentation- or DOM-defect ?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
