[infinispan-issues] [JBoss JIRA] (ISPN-1788) infinispan-5.1.xsd out of sync with StAX parser

[Paul Ferraro (JIRA)]

    [ https://issues.jboss.org/browse/ISPN-1788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12662442#comment-12662442 ] 

Paul Ferraro commented on ISPN-1788:
------------------------------------

Pete,
Unfortunately not - we have similar issues with our xsds getting out of sync with the parser.
The trouble is, your test will only ever detect missing bits from the xsd.  Obsolete optional elements/attributes will go unnoticed.
For basic schema validation:

SchemaFactory.newInstance(XMLConstants.W3C_XML_SCHEMA_NS_URI).newSchema(schemaFile).newValidator().validate(xmlFile);
                
> infinispan-5.1.xsd out of sync with StAX parser
> -----------------------------------------------
>
>                 Key: ISPN-1788
>                 URL: https://issues.jboss.org/browse/ISPN-1788
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Configuration
>    Affects Versions: 5.1.0.FINAL
>            Reporter: Paul Ferraro
>            Assignee: Pete Muir
>            Priority: Blocker
>             Fix For: 5.2.0.ALPHA1, 5.2.0.FINAL
>
>
> There are some inconsistencies between the infinispan-5.1.xsd schema in the 5.1.0.FINAL jar and the StAX parser.  Here are the ones I've noticed so far:
> 1. parser recognizes <stateTransfer/> element, which does not exist in the xsd
> 2. parser recognizes <storeAsBinary enabled="true|false"/> attribute, which does not exist in xsd
> I recommend you create a unit tests that validates a fully specified xml file against the schema.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira