[
https://issues.apache.org/jira/browse/AMQ-5383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14159751#comment-14159751
]
clebert suconic commented on AMQ-5383:
--------------------------------------
Is it worth to invest that on ActiveMQ 6? there is some support required for
reference countings on the server for temporary queues on the anonymous
subscriptions... I'm not sure how difficult it would be to impleent that on
ActiveMQ 6 (current master).
Maybe it could be a result of the merging between HornetQ and ActiveMQ which we
will be focusing now.
> JMS 2.0 Client APIs Support
> ---------------------------
>
> Key: AMQ-5383
> URL: https://issues.apache.org/jira/browse/AMQ-5383
> Project: ActiveMQ
> Issue Type: New Feature
> Components: JMS client
> Reporter: John D. Ament
>
> I'd like to propose improving upon ActiveMQ by adding client API support to
> the JMS client. One way to do this would be to throw out the current client
> JAR and replace it with a new one based on JMS 2. That wouldn't be a good
> idea, many people are happy to use JMS 1.1 and I feel we should let them
> continue.
> Antoher way is to create a new JAR, activemq-jm2-client, which extends the
> existing 1.1 client JAR for 2.0 APIs. This would allow the core activemq to
> remain on Java 6, and allow just this API JAR to be on Java 7 (due to the
> AutoCloseable requirement).
> I've already started putting together a geronimo spec jar for JMS 2 support.
> You can see that here:
> https://github.com/johnament/geronimo-specs/tree/jms2/geronimo-jms_2.0_spec
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
