You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ode.apache.org by Simone Maletta <si...@alice.it> on 2008/03/27 16:52:05 UTC
if activity
Hi guys,
I wrote this simple BPEL code to make a prove:
<if name="1">
<condition>true()</condition>
<assign>
<from>false()</from>
<to part="resp" variable="respMex"/>
</assign>
<invoke inputVariable="respMex" [...]/>
<else>
<assign>
<from>true()</from>
<to part="resp" variable="respMex"/>
</assign>
<invoke inputVariable="respMex" [...]/>
</else>
</if>
but nothing happens.
I know always the first brach shold be executed.
Where is the problem? There is someone may help me???
Thank you very much, regards
Simone
Re: onAlarm doesn't work for flows ??
Posted by Alex Boisvert <bo...@intalio.com>.
I would be surprised if this was a ServiceMix integration issue; it's most
likely an issue in the BPEL runtime if it exists.
If you can create a Jira issue that demonstrates the behavior, we'll look
into it.
thanks!
alex
On Tue, Apr 1, 2008 at 2:15 AM, Nowakowski, Mateusz <
Mateusz.Nowakowski@sabre-holdings.com> wrote:
> Yes, these instructions are invocations.
>
> I tested it also without flow activity and bpel returns after invoke
> activity, not after delay time.
>
> I used ode in async mode and under service mix.
>
> I think it may be ServiceMix integration issue.
>
> --
> Regards
> Mateusz Nowakowski
> -----Original Message-----
> From: matthieu.riou@gmail.com [mailto:matthieu.riou@gmail.com] On Behalf
> Of Matthieu Riou
> Sent: Friday, March 28, 2008 4:11 PM
> To: user@ode.apache.org
> Subject: Re: onAlarm doesn't work for flows ??
>
> Hi,
>
> At first sight it seems a bit odd as I'm not aware of any "classic"
> scenario
> that would put the alarm condition of an event handler on hold. But what
> are
> those 2 parallel long instructions exactly? Invocations? Maybe a bit
> more
> context would help me infer what the problem might be. Also can you
> reproduce it with a simple test process that I could use to see what's
> wrong?
>
> Thanks,
> Matthieu
>
> On 3/28/08, Nowakowski, Mateusz <Ma...@sabre-holdings.com>
> wrote:
> >
> > Hi all,
> >
> > I think that onAlarm doesn't work while performing flow instruction.
> >
> > I have for example onAlarm set for 5 seconds:
> > <bpel:eventHandlers>
> > <bpel:onAlarm>
> > <bpel:for>"PT5S"</bpel:for>
> > <bpel:scope>
> > <bpel:throw
> > faultName="tns:TimeoutFault"/>
> > </bpel:scope>
> > </bpel:onAlarm>
> > </bpel:eventHandlers>
> >
> > And I have
> > <bpel:flow>
> > ... Two parallel long instructions...
> > </bpel:flow>
> >
> > And I noticed that onAlarm is executed after <flow> instructions
> finish.
> > Not after 5 seconds.
> >
> > --
> > Regards
> >
> > Mateusz Nowakowski
> >
>
RE: onAlarm doesn't work for flows ??
Posted by "Nowakowski, Mateusz" <Ma...@sabre-holdings.com>.
Yes, these instructions are invocations.
I tested it also without flow activity and bpel returns after invoke
activity, not after delay time.
I used ode in async mode and under service mix.
I think it may be ServiceMix integration issue.
--
Regards
Mateusz Nowakowski
-----Original Message-----
From: matthieu.riou@gmail.com [mailto:matthieu.riou@gmail.com] On Behalf
Of Matthieu Riou
Sent: Friday, March 28, 2008 4:11 PM
To: user@ode.apache.org
Subject: Re: onAlarm doesn't work for flows ??
Hi,
At first sight it seems a bit odd as I'm not aware of any "classic"
scenario
that would put the alarm condition of an event handler on hold. But what
are
those 2 parallel long instructions exactly? Invocations? Maybe a bit
more
context would help me infer what the problem might be. Also can you
reproduce it with a simple test process that I could use to see what's
wrong?
Thanks,
Matthieu
On 3/28/08, Nowakowski, Mateusz <Ma...@sabre-holdings.com>
wrote:
>
> Hi all,
>
> I think that onAlarm doesn't work while performing flow instruction.
>
> I have for example onAlarm set for 5 seconds:
> <bpel:eventHandlers>
> <bpel:onAlarm>
> <bpel:for>"PT5S"</bpel:for>
> <bpel:scope>
> <bpel:throw
> faultName="tns:TimeoutFault"/>
> </bpel:scope>
> </bpel:onAlarm>
> </bpel:eventHandlers>
>
> And I have
> <bpel:flow>
> ... Two parallel long instructions...
> </bpel:flow>
>
> And I noticed that onAlarm is executed after <flow> instructions
finish.
> Not after 5 seconds.
>
> --
> Regards
>
> Mateusz Nowakowski
>
Re: onAlarm doesn't work for flows ??
Posted by Matthieu Riou <ma...@offthelip.org>.
Hi,
At first sight it seems a bit odd as I'm not aware of any "classic" scenario
that would put the alarm condition of an event handler on hold. But what are
those 2 parallel long instructions exactly? Invocations? Maybe a bit more
context would help me infer what the problem might be. Also can you
reproduce it with a simple test process that I could use to see what's
wrong?
Thanks,
Matthieu
On 3/28/08, Nowakowski, Mateusz <Ma...@sabre-holdings.com>
wrote:
>
> Hi all,
>
> I think that onAlarm doesn't work while performing flow instruction.
>
> I have for example onAlarm set for 5 seconds:
> <bpel:eventHandlers>
> <bpel:onAlarm>
> <bpel:for>"PT5S"</bpel:for>
> <bpel:scope>
> <bpel:throw
> faultName="tns:TimeoutFault"/>
> </bpel:scope>
> </bpel:onAlarm>
> </bpel:eventHandlers>
>
> And I have
> <bpel:flow>
> ... Two parallel long instructions...
> </bpel:flow>
>
> And I noticed that onAlarm is executed after <flow> instructions finish.
> Not after 5 seconds.
>
> --
> Regards
>
> Mateusz Nowakowski
>
onAlarm doesn't work for flows ??
Posted by "Nowakowski, Mateusz" <Ma...@sabre-holdings.com>.
Hi all,
I think that onAlarm doesn't work while performing flow instruction.
I have for example onAlarm set for 5 seconds:
<bpel:eventHandlers>
<bpel:onAlarm>
<bpel:for>"PT5S"</bpel:for>
<bpel:scope>
<bpel:throw
faultName="tns:TimeoutFault"/>
</bpel:scope>
</bpel:onAlarm>
</bpel:eventHandlers>
And I have
<bpel:flow>
... Two parallel long instructions...
</bpel:flow>
And I noticed that onAlarm is executed after <flow> instructions finish.
Not after 5 seconds.
--
Regards
Mateusz Nowakowski
Re: if activity
Posted by Matthieu Riou <ma...@offthelip.org>.
Hi Simone,
The problem is having two activities in the first branch, and <if> executes
only a single activity (which can be a sequence). So you should have:
<if name="1">
<condition>true()</condition>
<sequence>
<assign>
<from>false()</from>
<to part="resp" variable="respMex"/>
</assign>
<invoke inputVariable="respMex" [...]/>
</sequence.
<else>
<sequence>
<assign>
<from>true()</from>
<to part="resp" variable="respMex"/>
</assign>
<invoke inputVariable="respMex" [...]/>
</sequence.
</else>
</if>
On Thu, Mar 27, 2008 at 8:52 AM, Simone Maletta <si...@alice.it>
wrote:
> Hi guys,
> I wrote this simple BPEL code to make a prove:
> <if name="1">
> <condition>true()</condition>
> <assign>
> <from>false()</from>
> <to part="resp" variable="respMex"/>
> </assign>
> <invoke inputVariable="respMex" [...]/>
> <else>
> <assign>
> <from>true()</from>
> <to part="resp" variable="respMex"/>
> </assign>
> <invoke inputVariable="respMex" [...]/>
> </else>
> </if>
>
> but nothing happens.
> I know always the first brach shold be executed.
> Where is the problem? There is someone may help me???
> Thank you very much, regards
> Simone