You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "John D. Ament" <jo...@apache.org> on 2016/06/29 22:58:51 UTC
Interest in a JMS2 based client?
Hi Qpid Community!
I was wondering, is there any interest in upgrading the Qpid JMS client to
the JMS 2 specification?
There is an Alpha 2 of the JMS 2 spec, which is used by ActiveMQ Artemis
for its client libraries. I would love to see similar support in Qpid, and
would be happy to give a hand. If my name's unfamiliar, I was on the JMS 2
expert group.
John
Re: Interest in a JMS2 based client?
Posted by Robbie Gemmell <ro...@gmail.com>.
On 29 June 2016 at 23:58, John D. Ament <jo...@apache.org> wrote:
> Hi Qpid Community!
>
> I was wondering, is there any interest in upgrading the Qpid JMS client to
> the JMS 2 specification?
>
> There is an Alpha 2 of the JMS 2 spec, which is used by ActiveMQ Artemis
> for its client libraries. I would love to see similar support in Qpid, and
> would be happy to give a hand. If my name's unfamiliar, I was on the JMS 2
> expert group.
>
> John
Hi John,
There is interest, it is even something thats been showing signs of
bubbling on my todo list recently. We were originally aiming to go
straight to JMS 2.0 with the newer client but eventually decided
getting a 1.1 client out was more practical for various reasons. There
are also some non-trivial things to do around mapping some of the
added functionality on to AMQP 1.0, particularly such as the shared
subscription stuff which doesnt really have a natural fit.
Robbie
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org
Re: Interest in a JMS2 based client?
Posted by Steve Huston <sh...@riverace.com>.
Sorry for the confusion, John.
Qpid is not an OASIS-centric product, but it does implement a number of OASIS standards, including AMQP 1.0 itself.
TC discussions take part within OASIS which is completely separate from Apache and Qpid, though some people who work on Qpid (hi, Robbie ;-) also participate in OASIS. There are also OASIS participants from other vendors and groups.
-Steve
> On Jun 29, 2016, at 7:26 PM, John D. Ament <jo...@apache.org> wrote:
>
> Steve,
>
>> On 2016-06-29 19:13 (-0400), Steve Huston <sh...@riverace.com> wrote:
>> Hi John,
>>
>> I can't answer specifically for the code (though I suspect the answer will be yes), but I also chair the OASIS AMQP Bindings and Mappings technical committee. One of the TC's areas is standardizing the JMS mapping to AMQP 1.0 - weâ?Tre currently working on JMS 1.1 with JMS 2 a follow-on goal. Would you be willing to help out the TC ensure the standardized mapping reflects your experience and knowledge?
>
> I believe so. I think what you're looking for, to summarize in my own understanding, is that the specification of fields defined within JMS (e.g. headers) are mapped to the proper fields in AMQP?
>
> I don't know much about Qpid, is it an OASIS centric project? Or do discussions around this TC happen on this list?
>
>>
>> There's more info at https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=amqp-bindmap and I'd be happy to discuss it further if you like.
>>
>> Thanks,
>> -Steve Huston
>>
>>> -----Original Message-----
>>> From: John D. Ament [mailto:johndament@apache.org]
>>> Sent: Wednesday, June 29, 2016 6:59 PM
>>> To: dev@qpid.apache.org
>>> Subject: Interest in a JMS2 based client?
>>>
>>> Hi Qpid Community!
>>>
>>> I was wondering, is there any interest in upgrading the Qpid JMS client to the
>>> JMS 2 specification?
>>>
>>> There is an Alpha 2 of the JMS 2 spec, which is used by ActiveMQ Artemis for
>>> its client libraries. I would love to see similar support in Qpid, and would be
>>> happy to give a hand. If my name's unfamiliar, I was on the JMS 2 expert
>>> group.
>>>
>>> John
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
>> For additional commands, e-mail: dev-help@qpid.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
> For additional commands, e-mail: dev-help@qpid.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org
Re: RE: Interest in a JMS2 based client?
Posted by "John D. Ament" <jo...@apache.org>.
Steve,
On 2016-06-29 19:13 (-0400), Steve Huston <sh...@riverace.com> wrote:
> Hi John,
>
> I can't answer specifically for the code (though I suspect the answer will be yes), but I also chair the OASIS AMQP Bindings and Mappings technical committee. One of the TC's areas is standardizing the JMS mapping to AMQP 1.0 - we\u2019re currently working on JMS 1.1 with JMS 2 a follow-on goal. Would you be willing to help out the TC ensure the standardized mapping reflects your experience and knowledge?
I believe so. I think what you're looking for, to summarize in my own understanding, is that the specification of fields defined within JMS (e.g. headers) are mapped to the proper fields in AMQP?
I don't know much about Qpid, is it an OASIS centric project? Or do discussions around this TC happen on this list?
>
> There's more info at https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=amqp-bindmap and I'd be happy to discuss it further if you like.
>
> Thanks,
> -Steve Huston
>
> > -----Original Message-----
> > From: John D. Ament [mailto:johndament@apache.org]
> > Sent: Wednesday, June 29, 2016 6:59 PM
> > To: dev@qpid.apache.org
> > Subject: Interest in a JMS2 based client?
> >
> > Hi Qpid Community!
> >
> > I was wondering, is there any interest in upgrading the Qpid JMS client to the
> > JMS 2 specification?
> >
> > There is an Alpha 2 of the JMS 2 spec, which is used by ActiveMQ Artemis for
> > its client libraries. I would love to see similar support in Qpid, and would be
> > happy to give a hand. If my name's unfamiliar, I was on the JMS 2 expert
> > group.
> >
> > John
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
> For additional commands, e-mail: dev-help@qpid.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org
RE: Interest in a JMS2 based client?
Posted by Steve Huston <sh...@riverace.com>.
Hi John,
I can't answer specifically for the code (though I suspect the answer will be yes), but I also chair the OASIS AMQP Bindings and Mappings technical committee. One of the TC's areas is standardizing the JMS mapping to AMQP 1.0 - we’re currently working on JMS 1.1 with JMS 2 a follow-on goal. Would you be willing to help out the TC ensure the standardized mapping reflects your experience and knowledge?
There's more info at https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=amqp-bindmap and I'd be happy to discuss it further if you like.
Thanks,
-Steve Huston
> -----Original Message-----
> From: John D. Ament [mailto:johndament@apache.org]
> Sent: Wednesday, June 29, 2016 6:59 PM
> To: dev@qpid.apache.org
> Subject: Interest in a JMS2 based client?
>
> Hi Qpid Community!
>
> I was wondering, is there any interest in upgrading the Qpid JMS client to the
> JMS 2 specification?
>
> There is an Alpha 2 of the JMS 2 spec, which is used by ActiveMQ Artemis for
> its client libraries. I would love to see similar support in Qpid, and would be
> happy to give a hand. If my name's unfamiliar, I was on the JMS 2 expert
> group.
>
> John
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org