Hi Andreas,
I'm currently sticking to the distinction between listen / participant.
I have read carefully your message and I'm wondering if your case
involves making a process [segment] wait for an incoming message or
for the engine to wait for the incoming message to start a new
process.
In the first case (process segment waiting for a message), the
'listen' expression is currently (0.9.16) the right candidate :
---8<---
sequence do
# work before
listen :to => "offer_receiver"
# work after
end
--->8---
in this case, any message for the participant "offer_receiver" will
make the process resume. You can add restriction to which messages do
fit with the :where attribute.
This 0.9.16 version of the 'listen' expression may be bound to
participant names (topic names / channel names) that don't formally
exist (as registered participants).
'listen' will take care of the "flowExpressionId accouting" for you,
just make sure your ActiveMQListener hands a workitem with the
participant name set to "offer_receiver" to the engine. The fei can be
null.
In the second case, engine waiting for message to launch process, I
would recommend having the ActiveMQ subscriber filling a LaunchItem
and calling the launch method of the engine with it.
(I have reread your mail and it seems that you are interested in the
first case (listen)).
--
John Mettraux -///- http://jmettraux.openwfe.org
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"OpenWFEru dev" 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-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
