anonymous wrote : i would guess the whole purpose of an appserver is to take care of
making a global transaction out of XA transactional resources, no ? even if we would use
different DSs.
managing a global/distributed transaction is the app server's business indeed, except
that (1) some databases such as HSQL and (correct me if I'm wrong) MySQL do not
provide XA data sources and (2) the EJB timer service's support for 2PC relies on its
underlying data source, which affects the EntitySchedulerService. JMS's 2PC support
does not rely on the underlying data source's XA capability and therefore the
JmsMessageService is unaffected.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4176750#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...