John,
As you know this is a hot topic in the Wf-XML area.  We are currently
looking at a RESTFul approach to it and I owe you a document (coming
soon).  Short of sharing the document that is currently half-baked,
here is my current thoughts:

A remote engine is REST-accessible and any activity can easily launch
a remote process.
Calling activity would have access to remote process status & data
(using a GET).

Better, this calling activity could be exposed as a URI somehow and
subscribe to process event notification.  Calling activity waits for
response, gets the message and continues on.
This does not appear as a huge stumbling block...
V/R,
Pat.

On Aug 8, 8:21 pm, "John Mettraux" <[EMAIL PROTECTED]> wrote:
> On 8/8/07, Pat Cappelaere <[EMAIL PROTECTED]> wrote:
>
>
>
> > The specific activity of the running workflow could indeed execute a
> > sub-process.  In this particular case, I am more interested in execute a
> > workflow running on a different machine.
> > The activity would wait for resulting data.
>
> Hi Pat,
>
> thanks for the clarification.
> I haven't ported/rewritten the mechanisms for doing that from
> OpenWFEja to OpenWFEru.
>
> It was usually done by registering the remote engine as a participant.
> The workitem from the local engine to the remote engine would be
> transformed into a launchitem and dispatched to the remote engine (by
> the participant standing for it).
>
> I'd be glad to work on that again, to make OpenWFEru more complete
> (and powerful). Your input on that is much welcome. (We should maybe
> discuss that on the dev mailing list).
>
> Cheers,
>
> --
> John Mettraux   -///-  http://jmettraux.openwfe.org


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"OpenWFEru users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/openwferu-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to