Gathering information on subprocesses through ruote-rest

1 view
Skip to first unread message

Patrick

unread,
Jul 10, 2009, 3:12:10 PM7/10/09
to Ruote (OpenWFEru) users
While I was experimenting with subprocesses, I ran into a problem with
getting information on the state of the subprocess through ruote-rest.
If I submit a (relatively) simple process:

class Test0 < OpenWFE::ProcessDefinition
sequence do
subprocess :ref => "http://locahost/test_process2.rb"
participant :ref => "alpha"
end
end

where http://localhost/test_process2.rb is:

class Test1 < OpenWFE::ProcessDefinition
sequence do
participant :ref => "bravo"
end
end

and alpha and bravo are active participants, the process submits fine
(for this example, we'll call the resulting process 20090710-
kikenapaju).

Checking GET /processes/20090710-kikenapaju, I get information on
Test0, but there doesn't seem to be a way to see what's going on
inside Test1. If I check GET /workitems, I can see there is a
workitem named 20090710-kikenapaju.0/0_0_0 (which I assume is the one
inside Test1 for this process), but when I try GET /workitems/20090710-
kikenapaju.0/0_0_0, I receive the following message:

File not found: /workitems/20090710-kikenapaju.0/0_0_0

Because the participant in Test1 is an active participant, if I can't
GET/PUT to it, the process just waits indefinitely. Is there a way to
do the GET/PUT I need, or can subprocesses not have active
participants in them?

Thanks!

John Mettraux

unread,
Jul 10, 2009, 7:56:16 PM7/10/09
to openwfe...@googlegroups.com
On Sat, Jul 11, 2009 at 4:12 AM, Patrick<patrick...@gmail.com> wrote:
>
> Checking GET /processes/20090710-kikenapaju, I get information on
> Test0, but there doesn't seem to be a way to see what's going on
> inside Test1.  If I check GET /workitems, I can see there is a
> workitem named 20090710-kikenapaju.0/0_0_0 (which I assume is the one
> inside Test1 for this process), but when I try GET /workitems/20090710-
> kikenapaju.0/0_0_0, I receive the following message:
>
> File not found: /workitems/20090710-kikenapaju.0/0_0_0
>
> Because the participant in Test1 is an active participant, if I can't
> GET/PUT to it, the process just waits indefinitely.  Is there a way to
> do the GET/PUT I need, or can subprocesses not have active
> participants in them?

Hello Patrick,

you have found a serious bug in ruote-rest, it's unable to present
workitems (and expressions) belonging to subprocesses.

http://github.com/jmettraux/ruote-rest/issues#issue/5

I will try to fix that ASAP and we will make sure this issue doesn't
appear in the upcoming ruote-kit.


Many thanks,

--
John Mettraux - http://jmettraux.wordpress.com

John Mettraux

unread,
Jul 13, 2009, 12:49:53 AM7/13/09
to openwfe...@googlegroups.com
On Sat, Jul 11, 2009 at 8:56 AM, John Mettraux<jmet...@openwfe.org> wrote:
> On Sat, Jul 11, 2009 at 4:12 AM, Patrick<patrick...@gmail.com> wrote:
>
>> Because the participant in Test1 is an active participant, if I can't
>> GET/PUT to it, the process just waits indefinitely.  Is there a way to
>> do the GET/PUT I need, or can subprocesses not have active
>> participants in them?
>
> you have found a serious bug in ruote-rest, it's unable to present
> workitems (and expressions) belonging to subprocesses.
>
>  http://github.com/jmettraux/ruote-rest/issues#issue/5
>
> I will try to fix that ASAP and we will make sure this issue doesn't
> appear in the upcoming ruote-kit.

Hello Patrick,

I have fixed (well my tests seem to indicate I have) the issue.

Two commits were required :

ruote : http://github.com/jmettraux/ruote/commit/2ca67d78cc440f5e61861718595046f9f99e52e0
ruote-rest : http://github.com/jmettraux/ruote-rest/commit/5467a3e97e70bee7a89c02ef2939518d3ab0e6d4

Please tell me if there are still remaining issues and I'll fix them.


Thanks again,

Patrick Clark

unread,
Jul 14, 2009, 8:01:09 PM7/14/09
to openwfe...@googlegroups.com
>
> Two commits were required :
>
>  ruote : http://github.com/jmettraux/ruote/commit/2ca67d78cc440f5e61861718595046f9f99e52e0
>  ruote-rest : http://github.com/jmettraux/ruote-rest/commit/5467a3e97e70bee7a89c02ef2939518d3ab0e6d4
>
> Please tell me if there are still remaining issues and I'll fix them.

Hi John,
Thanks for the quick fix! I'll be sure to let you know if I run
into any other issues as I test these updates.

Thanks,
Patrick

Reply all
Reply to author
Forward
0 new messages