Jouni Juutinen wrote:
> Does anyone have experiences of MQSeries participating in EJB
> transactions? For example if one transaction includes Entity Bean
updating
> database table (JDBC) and a Entity or Session Bean inserting a message
> into MQSeries queue. Obviously I would like this whole transaction to
> commit or rollback as one entity. I quess this would require
transactional
> resource manager for MQSeries. Native MQSeries access (MQSeries binding
> for Java) supports syncpoints but that's not JTS compliant. Do I have to
> wait for JMS-version of MQSeries (when that one will be available?)?
As you say, it is highly desireable that the putting and getting of
messages to queues can be committed or backed out under syncpoint control
and this does indeed require that MQSeries be a transactional resource
manager.
In fact MQSeries is already a transactional resource manager supporting the
(pre-java) open standard for coordination of transactional resource
managers, XA. Unfortunately, no EJB servers today are based on XA, hence no
there is currently no coordination between MQSeries and EJBs.
This will be resolved soon, not sadly by EJB servers supporting XA, because
Sun is promoting the java-only JTA standard for achieving exactly the same
thing(*). Hence MQSeries will support JTA in a future release and will
thereby be able to be coordinated by any JTA-compliant EJB server.
You will not have to wait for MQSeries support of JMS - the two items are
unrelated.
(*) Who was it who said "the computer industry is totally committed to
standards - that is why we have so many of them"?
Ian McCallion
CICS Business Unit
IBM Hursley
[EMAIL PROTECTED]
Tel: ++44-1962-818065
Fax: ++44-1962-818069
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
