+1
Regards
JB
On 06/15/2015 03:28 PM, tmy...@wellsfargo.com wrote:
I would also like to see ActiveMQ support JMS 2.0. I have run into an issue
integrating ActiveMQ with WebSphereMQ related to JMS 2.0. The latest
WebSphereMQ client libraries version 8.0.0.2 are JMS 2.0 compliant. The
8.0.02
GitHub user cshannon opened a pull request:
https://github.com/apache/activemq/pull/115
https://issues.apache.org/jira/browse/AMQ-5843
Adding a new property on PolicyEntry called includeBodyForAdvisory which
will
include the original message body when sending advisory messages
I would also like to see ActiveMQ support JMS 2.0. I have run into an issue
integrating ActiveMQ with WebSphereMQ related to JMS 2.0. The latest
WebSphereMQ client libraries version 8.0.0.2 are JMS 2.0 compliant. The
8.0.02 version addresses security vulnerabilities and provides support for
TLS
GitHub user clebertsuconic opened a pull request:
https://github.com/apache/activemq-artemis/pull/28
ARTEMIS-136 - XA Error fix with proper exception error
https://issues.apache.org/jira/browse/ARTEMIS-136
From what I researched from implementers of XA TM if you throw ERR
Github user clebertsuconic commented on the pull request:
https://github.com/apache/activemq-artemis/pull/28#issuecomment-112208540
I aborted the build manually since there was a new one coming, ignore build
429
---
If your project is set up for it, you can reply to this email and
Please check the following (vote up if necessary). There's obviously
duplication.
Cheers,
Hadrian
[1] https://issues.apache.org/jira/browse/AMQ-5383
[2] https://issues.apache.org/jira/browse/AMQ-5736
[3] https://issues.apache.org/jira/browse/GERONIMO-6455
On 06/15/2015 09:28 AM,
[3] = it's fixed already... it should be closed as done!
[1] == [2]
The implementation of the JMS2 client api is trivial. you could
actually copy paste it from Artemis into ActiveMQ5 as a backport.
the only issue is the subscription modes added by JMS2 that will need
some extra reference
