asked on
How to parse <assert> tag in XSD1.1 using XSOM Parser?
I have been using XSOM parser (xsom-20140925.jar) for parsing XSD 1.0 and able to achieve parsing all xs:elements and restrictions (like pattern, minOccurs etc..).
Lately our XSD1.0 been upgraded to version XSD1.1, where new <assert> tag been included. My XSOM parser fails to identify this assert tag and throws the following exception.
Could not parse the inputstream: org.xml.sax.SAXParseExcept
Any help and suggestions would help me solve the issue.
Thanks.
Lately our XSD1.0 been upgraded to version XSD1.1, where new <assert> tag been included. My XSOM parser fails to identify this assert tag and throws the following exception.
Could not parse the inputstream: org.xml.sax.SAXParseExcept
Any help and suggestions would help me solve the issue.
Thanks.
XMLJava
Last Comment
Gertone (Geert Bormans)
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
Please accept https:#a41141126 as the answer
This question has been answered completely and this is an important question + answer to have in the database
assertions have been a long wanted feature for XML schema
with the advent of XSD1.1 assertions have been included to the schema language
but even after all this time, there are only two parsers that really support it
This is tricky because as you can see from the question, the feature is a very tempting extension to the language. Many people try to use it but their toolset does not allow that. All options as a resolution have been given in my first response. Please accept
This question has been answered completely and this is an important question + answer to have in the database
assertions have been a long wanted feature for XML schema
with the advent of XSD1.1 assertions have been included to the schema language
but even after all this time, there are only two parsers that really support it
This is tricky because as you can see from the question, the feature is a very tempting extension to the language. Many people try to use it but their toolset does not allow that. All options as a resolution have been given in my first response. Please accept
Not enough information to confirm an answer.