On Tue, May 13, 2014 at 8:01 PM, uromahn <[email protected]> wrote:
> Hi Folks,
>
> just wanted  to throw a bone out seeing if anyone catches it and responds.
>
> I was wondering whether ActiveMQ has any intention to support the JMS 2.0
> API specification which is part of JEE7 and has been released almost a year
> ago (May 21, 2013).
>
> JMS 2.0 has some significant improvements over JMS 1.1 and I believe
> supporting it in ActiveMQ soon may improve its popularity within the Java
> community.
>
> Based on my current investigation, the only options for JMS 2.0 support seem
> to be HornetQ (JBoss) and Open MQ (Glassfish) and Fiorano MQ.
>
> So, is there any interest in supporting JMS 2.0 in the near future? I would
> love to contribute but my current day-job just doesn't give me enough time.
> :(

JMS 2.0 is not on the radar for ActiveMQ 5.10.
And I think people are too busy with getting the final fixes and
whatnot needed for that release.

I suggest you log a JIRA ticket about JMS 2.0 support, if not already
there. And use its voting system, so people can say they want this.

Also what is there in JMS 2.0 from "broker point of view". eg for
client there is a simpler api. But what is there on the broker side?

Also a lot of other protocols these days get attention than just JMS.
eg MQTT, AMQP, etc. IMHO these are more important in the future, than
traditional JMS. And most clients/brokers is already 1.1 compliant.

So I don't see this as a show stopper that 2.0 must be support in the
very near future.

But sure it would be great for ActiveMQ to support that too.

>
> Ideas, comments, suggestions?
> -Uli
>
>
>
> --
> View this message in context: 
> http://activemq.2283324.n4.nabble.com/Discussion-JMS-2-0-API-support-tp4681089.html
> Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.



-- 
Claus Ibsen
-----------------
Red Hat, Inc.
Email: [email protected]
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
hawtio: http://hawt.io/
fabric8: http://fabric8.io/

Reply via email to