JMS Outbound with Connector 1.5

Hi,

according to the spec the app component looks up a
javax.resource.cci.ConnectionFactory and obtains a
javax.resource.cci.Connection. The latter is actually a handle to the
physical (Managed) connection.

To use the EIS, the app component casts the javax.resource.cci.Connection to
the resp. EIS connection and uses that. Is that right till here?

Now with a JMS RA I would expect the javax.resource.cci.Connection is a
javax.jms.Connection (JMS 1.1) and thus the app component casts it to this
type. However, this is not possible because both
javax.resource.cci.Connection and javax.jms.Connection are incompatible.
They throw different exceptions on close and return different MetaData.

Also I would assume that outbound JMS messaging via a RA is specified
somewhere. I don't find it in the specs. If that is not specified then the
API is not standardized via a RA and in a worst case an app component has to
change its code if the JMS vendor changes.

Or is the JMS pluggability only for message inflow? That would be indeed a
big disadvantage.

Could someone clearify, please?

Thanks,
Andreas

--
Andreas Mueller
IIT GmbH, Bremen/Germany
http://www.swiftmq.com

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