Posted
almost 5 years
ago
by
Angelo
Hi all,
I consume XSCMValidator API to manage completion in XML editor based on XML Schema by taking care of existing XML elements and filter available elements according XML Schema constraints.
It works great except whis xs:all in XSD 1.1 and Read more
|
Posted
almost 5 years
ago
by
John Ferguson
xercesImpl.jar does not adhere to the java 11 module system
|
Posted
almost 5 years
ago
by
Mukul Gandhi
While using XSD 1.1, full XPath 2.0 with CTA doesn't work in certain cases
|
Posted
almost 5 years
ago
by
Mukul Gandhi
Xerces-J 2.12.0: XSD 1.1 CTA validation errors
|
Posted
almost 5 years
ago
by
Mukul Gandhi
Xerces-J 2.12.0: XSD 1.1 CTA validation errors
|
Posted
about 5 years
ago
by
Radu Coravu
Non-ASCII characters should be allowed when constructing URIs.
This works:
new java.net.URI("http://host/webdav/6发给亿科的样例维修手册底.dita");
but the org.apache.xerces.util.URI is more restrictive to the characters allowed in an URI path.
In my opinion Read more
|
Posted
about 5 years
ago
by
Radu Coravu
Non-ASCII characters should be allowed when constructing URIs.
This works:
new java.net.URI("http://host/webdav/6发给亿科的样例维修手册底盘系统\\\\ESP控制系统/测试副本.dita");
but the org.apache.xerces.util.URI is more restrictive to the characters allowed in an URI Read more
|
Posted
about 5 years
ago
by
Robin Verduijn
Perhaps another solution would be to take the org.w3c.dom.* classes out of xercesImpl.jar and put them in a separate xercesImpl-deps.jar, then uploading a new xercesImpl.jar with a .pom file declaring a dependency on that? Done that way, people can Read more
|
Posted
over 5 years
ago
by
Mukul Gandhi
Certain XSD 1.1 assert evaluations earlier, produced error messages containing strings like following,
FOAR0001 - Division by zero
The hyphen in such error messages, can be confused with a negation symbol. The hyphen should be replaced with Read more
|
Posted
over 5 years
ago
by
Mukul Gandhi
XSD 1.1 assert error message improvements
|