tag:blogger.com,1999:blog-4309414151374220630.post734527244779815871..comments2023-07-04T12:59:09.183+02:00Comments on Process Developments: How To Send XA JMS Message On JBossTom Baeyenshttp://www.blogger.com/profile/03067067751334471585noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-4309414151374220630.post-37065121760638604672012-02-24T09:27:30.854+01:002012-02-24T09:27:30.854+01:00If you really want distributed transaction with ot...If you really want distributed transaction with other resources like JDBC, you have to lookup "java:/JmsXA" to get your ConnectionFactory. Other connection factories implements only "local" transaction.Yves Martinhttps://www.blogger.com/profile/07124885262076125657noreply@blogger.comtag:blogger.com,1999:blog-4309414151374220630.post-41063661226425167262009-12-24T10:17:52.856+01:002009-12-24T10:17:52.856+01:00Anonymous, thanks! JMS apis are more twisted then...Anonymous, thanks! JMS apis are more twisted then I already thought. We're now checking how we can accomodate both XA and non-XA jms message sending.Tom Baeyenshttps://www.blogger.com/profile/03067067751334471585noreply@blogger.comtag:blogger.com,1999:blog-4309414151374220630.post-35715246414868817362009-12-23T21:11:45.496+01:002009-12-23T21:11:45.496+01:00Actually the article is about sending messages in ...Actually the article is about sending messages in a transacted way that has nothing to do with XA. If you want to use XA, simply lookup the XAFactory, create an XASession (which does not provide the transactional options for obvious reasons) and that's it!<br />Using standard (non-XA) Sessions is also not really potable between App-Servers.Anonymousnoreply@blogger.com