[ 
https://issues.apache.org/jira/browse/XERCESJ-1573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13414491#comment-13414491
 ] 

Mukul Gandhi commented on XERCESJ-1573:
---------------------------------------

My guess is, that every usage of XSD 1.1 assertions may not result in same 
performance problem that you've reported. Perhaps the performance problem that 
you've reported, is related to specific class of XPath expressions (for e.g, 
that build date objects or do date arithmetic) -- perhaps you can help us 
identify these things.


As a second check, you may do for e.g same performance tests with following XSD 
type definitions,

<!-- tests if a number is even -->
<xs:simpleType name="evenNumber">
     <xs:restriction base="xs:integer">
          <xs:assert test="$value mod 2 = 0"/>
     </xs:restriction>
</xs:simpleType>


<!-- enforce cardinality of a sequence via an assertion -->
<xs:complexType>
     <xs:sequence>
          <xs:element name="a" type="xs:string" maxOccurs="unbounded"/>
     </xs:sequence>
     <xs:assert test="count(a) = 5"/>
</xs:complexType>


and report to us the results.
                
> Possible memory leak when using assertions
> ------------------------------------------
>
>                 Key: XERCESJ-1573
>                 URL: https://issues.apache.org/jira/browse/XERCESJ-1573
>             Project: Xerces2-J
>          Issue Type: Bug
>          Components: XML Schema 1.1 Datatypes
>    Affects Versions: 2.11.0
>            Reporter: Jorge L. Williams
>            Priority: Blocker
>         Attachments: d1.png, d2.png, duration-sans-assert.xsd, duration.xsd, 
> good.xml
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to