I think I have already answered in another thread, but i'll try to be more
clear.

First, send and sendSync is not related to the MEP.
When you use send, the exchange (DONE status or answer for an InOut mep)
will
come back to the delivery channel of the component, where messages are
dequeued
by the component and processed.
When using sendSync, the JBI container will wait for this answer in a
blocking call (so you
can not use sendSync when sending a DONE status).

Now, if the POJO would use send (and not sendSync), the component will
receive the exchange
back and should give it back to the pojo.  There is currently no way to do
that (even if we could imagine some).  So currently, you are limited to use
sendSync on ACTIVE exchanges and send
on DONE or ERROR exchanges.

To handle async send from a POJO, the POJO would need to pull exchanges from
the delivery channel (the component need to wrap it to only give the
exchanges that this very POJO has send, but the wrapper is already done) or
that the component implements the MessageExchangeListener interface for
example.
Please, feel free to raise a JIRA if you need that.

Cheers,
Guillaume Nodet

On 6/15/06, Alessandro Fredianelli <[EMAIL PROTECTED]>
wrote:

every time i try an asynchronous send from a jsr181 pojo a get error on
the MEP.
I'm only allowed to do synch sends.
Is this right? What does the synch send really imply?

Reply via email to