[
https://issues.jboss.org/browse/ISPN-1788?page=com.atlassian.jira.plugin....
]
Paul Ferraro updated ISPN-1788:
-------------------------------
Description:
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.
was:
There are some inconsistencies between the infinispan-5.1.xsd schema in the 5.1.0.FINAL
jar and the StAX parser. Here are a few inconsistencies 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.
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: Manik Surtani
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