Re: AW: Inbound / Outbound communication in JCA 1.5

"Gyhra, Norman" wrote:
>
> David,
>
> We have obviously misunderstood each other.
> I am aware that you need some form of multi-threading
> for a listener waiting for incoming calls.
> And yes, the Work Management Contract provides
> a handy mechanism to deal with multi-threading.
>
> However, my initial question had a different aim.
> See my reply to Jim.
>
> The problem that I see is that I don't know if
> an incoming call is synchronous or asynchronous
> and the Message Inflow Contract seems to be clearly
> aimed at asynchronous messaging.

the Message Inflow is a generic contract that provides a tightly-coupled
mechanism between the container and the RA to make inbound invocations. Whether
the caller (outside) is using a sychronous or asynchrnous invocation model
should not matter - it is a private contract between the RA and its client.

The chapter "EJB invocation" describes how the message inflow contract is used
to make EJB invocations.

Ram

===========================================================================
To unsubscribe, send email to [email protected] and include in the body
of the message "signoff CONNECTOR-INTEREST".  For general help, send email to
[email protected] and include in the body of the message "help".