[
https://issues.apache.org/jira/browse/XERCESJ-1687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16328843#comment-16328843
]
Mukul Gandhi commented on XERCESJ-1687:
---------------------------------------
@Stephan:
I ran your test case, using the following example.
XML:
<?xml version="1.0"?>
<X>
<a>10</a>
<b>50</b>
</X>
XSD:
<?xml version="1.0"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema";>
<xs:element name="X">
<xs:complexType>
<xs:sequence>
<xs:element name="a" type="xs:integer"/>
<xs:element name="b" type="xs:integer"/>
</xs:sequence>
<xs:assert test="a le b"/>
</xs:complexType>
</xs:element>
</xs:schema>
I get result, as you're expecting (i.e both test cases pass).
Therefore, this bug you've indicated in PsychoPath processor, is not present
for all possible <assert> uses.
> 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: JAXP (javax.xml.validation)
> 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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
