[prev in list] [next in list] [prev in thread] [next in thread] 

List:       activemq-dev
Subject:    [jira] [Resolved] (AMQ-3479) The documentation should point-out
From:       "Timothy Bish (JIRA)" <jira () apache ! org>
Date:       2011-08-31 12:28:10
Message-ID: 538031357.2302.1314793690597.JavaMail.tomcat () hel ! zones ! apache ! org
[Download RAW message or body]


     [ https://issues.apache.org/jira/browse/AMQ-3479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel \
]

Timothy Bish resolved AMQ-3479.
-------------------------------

    Resolution: Fixed

Added a note to the XA section of the specified page.

> The documentation should point-out ActiveMQ's currently limitations with XA
> ---------------------------------------------------------------------------
> 
> Key: AMQ-3479
> URL: https://issues.apache.org/jira/browse/AMQ-3479
> Project: ActiveMQ
> Issue Type: Bug
> Components: Documentation
> Affects Versions: 5.5.0
> Reporter: Steve Smith
> 
> The documentation [explicitly \
> recommends|http://activemq.apache.org/should-i-use-xa.html] using XA transactions \
> for multiple resources: {quote}
> If you are using more than one resource; e.g. reading a JMS message and writing to \
> a database, you really should use XA - its purpose is to provide atomic \
> transactions for multiple transactional resources. {quote}
> However it fails to mention that XA support in ActiveMQ [does not support|AMQ-3022] \
> suspending/resuming transactions, e.g. with Springs Propagation.REQUIRES_NEW.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


[prev in list] [next in list] [prev in thread] [next in thread]