[
https://issues.apache.org/jira/browse/XERCESJ-1687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16273415#comment-16273415
]
Stephan Trebels commented on XERCESJ-1687:
------------------------------------------
Oh come on! That would kill performance altogether. Then you could also load
the xpath engine using its own classloader, and fix performance that way.
Ugly, but performant. I submitted the bug to Eclipse and Jesper has agreed to
the bug and the need for a fix. The only q is whether the fix will end up on
the old branch as well, which I intend to ask for.
If Eclipse does not agree to backport the fix (trivial as it is), then it'd be
better to fork the old eclipse xpath, that Xerces is using, and fix it there
(until Xerces does indeed move to the newer xpath2 syntax).
> XSD 1.1 validation with xs:assert is not thread safe
> ----------------------------------------------------
>
> Key: XERCESJ-1687
> URL: https://issues.apache.org/jira/browse/XERCESJ-1687
> Project: Xerces2-J
> Issue Type: Bug
> Components: XML Schema 1.1 Structures
> Affects Versions: 2.12.0
> Environment: java 8 / java 9
> Reporter: Stephan Trebels
> Priority: Critical
> Attachments: parallel-test.zip
>
>
> The XSD 1.1 validation code uses eclipse webtools xpath to validate
> assertions. The PsychoPath XPath 2.0 engine has a bug in
> ResultSequenceFactory, which invalidates correct execution in all parallel
> invocation of XSD 1.1 validation.
> This issue affects completely unrelated schemas and input XML, as long as
> both use assertions. The effect is a lot of spurious assert violations. The
> issue is visible even if only two threads are used in parallel.
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=527812
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
