AW: Inbound / Outbound communication in JCA 1.5

Hi Jim!

Thanks for your reply.


>>* Asynchronous outbound:
>>   How can I initiate asynchronous communication
>>   with an EIS using the Connector Architecture?
>
>It all depends on how your Resource Adapter (RA) is implemented and
>communicates with the EIS.  If it sends a message to the EIS in a
>non-blocking/asynchronous way, that's just fine.

Ok, but this also possible in JCA 1.0.
I hoped that JCA 1.5 might offer a way to control
or find out whether the communication is going to be
synchronous or asynchronous. The InteractionVerb
property of the InteractionSpec would have been a good
facility.


>>* Synchronous inbound:
>>   How can my J2EE application be synchronously called
>>   by an EIS through the Connector Architecture?
>
>With 1.5, RAs can access EJBs just like other application
> components.  This could enable the synchronous inbound
> you're looking for.

You are probably referring to the Message Inflow Contract.
However, when I read the specification, it says on page 144:

"The message producer generally is not interested in
the outcome of message processing by consumers.
However, it is possible that it may care to know if
the message has been consumed or not."

That does not sound to me as though request-reply is
a recommended way to use this contract.

Does my EJB receive any information whether the EIS
is waiting for a reply? I guess this is vendor-specific
then.


Regards,
Norman

===========================================================================
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".