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

Hudson commented on ODE-991:
----------------------------

SUCCESS: Integrated in ODE-trunk-jdk6 #855 (See 
[https://builds.apache.org/job/ODE-trunk-jdk6/855/])
fixes ODE-991. Thanks to Ciaran Jessup for the patch. (vanto: rev 
768cb6dcee7f97a2d606ea7ae60f35a79e03238d)
* 
bpel-runtime/src/test/java/org/apache/ode/bpel/elang/xpath20/runtime/XPath20ExpressionRuntimeTest.java
* 
bpel-runtime/src/main/java/org/apache/ode/bpel/elang/xpath20/runtime/JaxpFunctionResolver.java
* bpel-runtime/src/test/resources/xpath20/variables.xml


> ode:delete fails when removing multiple elements
> ------------------------------------------------
>
>                 Key: ODE-991
>                 URL: https://issues.apache.org/jira/browse/ODE-991
>             Project: ODE
>          Issue Type: Bug
>          Components: BPEL Runtime
>    Affects Versions: 1.3.2
>         Environment: Currently running r832808 with a couple of local patches.
>            Reporter: Ciaran Jessup
>            Assignee: Tammo van Lessen
>            Priority: Minor
>             Fix For: 1.3.7
>
>         Attachments: FixDeleteForMultipleElements.patch
>
>
> If ode:delete($Foo/x:child) returns multiple elements for deletion my 
> workflow fails with a selectionFailure :( 
> It seems to be caused by the Delete method being passed a SequenceExtent 
> rather than the expected List etc. 
> Whilst adding in support for that type (not sure why this only affects me ?) 
> I also found that the logic for removing child elements from the cloned 
> element that the function returns was squiffy.  It seemed as if it was 
> mutating the collection so the position offsets were incorrect and the wrong 
> elements would get removed from the parent element.  I've updated the code to 
> resolve that too (there is a better solution as alluded to in my code 
> comments in the patch)
> Ironically? I've stopped using ode:delete even with my 'fixes' and moved to 
> use an XSL transform as this turned out to be more memory efficient when 
> doing multiple deletes so I'm just providing my fixes back in case anyone 
> else needs / wants them.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to