Hi John,
I wonder if modifying LocalParticipant to handle a special "hash"
would be a good way to keep the logic and the navigation
'separated'... Now we could have something like this:
participant :ref => "form_A",
:nav => {:wait_for_next_form => true} # special "hash"
participant :ref => "web_service_Foo",
participant :ref => "form_B",
:nav => {:wait_for_next_form => false}
Then, we modify LocalParticipant to call a special consume method that
processes only :nav param, probably a XMPP notification for our
client. Then, after this, the "real" participant consume is called.
That way, every participant, even "automatic" ones, could notify stuff
to the client (just after the workitem is applied by the engine) just
by including the special param :nav.
Well, may be all this is silly. I'm just trying to figure out the best
way to deal with this issue...
Best regards!
Gonzalo.
On Nov 23, 9:54 am, Gonzalo <[email protected]> wrote:
> Hi John,
>
> Many thanks for the quick answer and suggestions.
>
> Best reagards,
> Gonzalo.
--
you received this message because you are subscribed to the "ruote users" group.
to post : send email to [email protected]
to unsubscribe : send email to [email protected]
more options : http://groups.google.com/group/openwferu-users?hl=en
