[
https://issues.apache.org/jira/browse/ODE-337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josef Spillner updated ODE-337:
-------------------------------
Attachment: testcase.bpel
Based on your comments and suggestions I've updated the testcase BPEL file,
which is attached. It contains a few more comments as well now.
The round() issue only happens for XPath 1.0, but goes away when using XPath
2.0. If both implementations are not schema-aware, then it looks indeed like
a bug in the XPath 1.0 handling to me.
On the mailing list it was recently suggested to use [position()=X] instead of
[X] to access individual elements from a sequence. This doesn't seem to
change anything in my case, and should also not be necessary according to the
XPath spec since both expressions are semantically equivalent.
> Several XPath-related issues: selection, rounding and message validation
> (3-in-1 report)
> ----------------------------------------------------------------------------------------
>
> Key: ODE-337
> URL: https://issues.apache.org/jira/browse/ODE-337
> Project: ODE
> Issue Type: Bug
> Components: BPEL Runtime
> Affects Versions: 1.2
> Reporter: Josef Spillner
> Attachments: ode-testcase-process.tar.gz, testcase.bpel
>
>
> After having had several issues with one of my processes, I tried to isolate
> the bugs and have put them into an easy-to-understand testcase process.
> The main bug contained in it is that a nodeset selection like A[0] doesn't
> work correctly even if A contains two nodes.
> To prove that two nodes are contained, I used the XPath count() function,
> which for some reason returns a floating point number, and even after
> round()ing it the number remains non-integer. This is the second bug.
> To be able to return the number of nodes in the BPEL reply despite the
> message not conforming to its schema is also interesting. I think it's useful
> but by default messages should be validated against their schema. This is the
> third bug.
> If the bugs are confirmed, I could open up dedicate bug reports for them, but
> I think at least the first two are related.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
