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

Michael Glavassevich commented on XERCESJ-1296:
-----------------------------------------------

Hi Ludger, 

It would be better to open a new JIRA issue since it sounds like you've found a 
different performance bottleneck than the one that was fixed here.

Thanks.

> ElementNSImpl.getBaseURI has exponential execution time relative to the depth 
> of the node in the document
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: XERCESJ-1296
>                 URL: https://issues.apache.org/jira/browse/XERCESJ-1296
>             Project: Xerces2-J
>          Issue Type: Improvement
>          Components: DOM (Level 3 Core)
>    Affects Versions: 2.9.1
>            Reporter: Ludger Bünger
>            Assignee: Michael Glavassevich
>            Priority: Minor
>             Fix For: 2.10.0
>
>         Attachments: ElementNSImplPatch.txt
>
>
> When using the Namespace-aware implementation, getBaseURI upon ElementNSImpl 
> unnecessarily calls getBaseURI twice upon its parent node (once upon "parent" 
> and once upon "ownerNode") resulting in an exponential execution time 
> relative to the depth of the node (since the number of calls to their 
> respective parent method doubles with each level of invocation).
> Elena Litani solved this already for ElementImpl, the same patch should be 
> applied to ElementNSImpl too.
> Solution: Apply the same patch to ElementNSImpl Elena Litani already applied 
> to ElementImpl in svn build 319554 (see 
> http://svn.apache.org/viewvc/xerces/java/trunk/src/org/apache/xerces/dom/ElementImpl.java?r1=319502&r2=319554)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

Reply via email to