ode-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alex Boisvert <boisv...@intalio.com>
Subject Re: foreach counter boundaries
Date Thu, 19 Mar 2009 04:51:30 GMT
I believe this was fixed in 1.3+.

alex


On Wed, Mar 18, 2009 at 6:05 PM, Andi Abes <aabes@progress.com> wrote:

> It appears that ODE 1.2 wants to see strings for counter values, e.g.:
> <forEach>
> <startCounterValue>"1"</startCounterValue>
> <finalCounterValue>$BPELMessage.serial-iterations</finalCounterValue>
>
> The quoted version works, but if the value is specified as just 1 or
> even number(1) it seems to be interpreted as 0.
> Is this expected?
>
>
> From reading too many specs....it appears that the bpel executable
> schema defines the content of these elements as tExpression, with no
> real restriction on the content, while  the text itself uses the
> following:
>
> <startCounterValue expressionLanguage="anyURI"?>
> unsigned-integer-expression </startCounterValue>
> <finalCounterValue expressionLanguage="anyURI"?>
> unsigned-integer-expression </finalCounterValue>
>
> Which lead me to expect that bear numbers and expressions should work...
> Thoughts?
>
>
>
>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message