Proton-based AMQP 1.0 JMS client

[Robbie Gemmell <ro...@gmail.com>]

Hi all,

As most of you will be aware, we currently have a JMS client that supports
AMQP 0-8 / 0-9 / 0-9-1 / 0-10 and a separate JMS client supporting AMQP
1.0, the latter of which was partly the result of prototyping work relating
to implementing AMQP 1.0. Since then Proton has been created, in part to
offer a means for ourselves and others integrate AMQP 1.0 into products. We
are already using Proton-c as basis for the AMQP 1.0 support for the C++
client and broker, but are not as yet using Proton-J within a Qpid client
or broker (though it is being used by the ActiveMQ project).

The time has come where we would like to begin working on a Proton-based
JMS[2.0] client. I have recently spent some time with Rob Godfrey working
through how we could approach this, putting together a very simple client
proof of concept using Proton-J. We are now reaching the point where we
would like to actually set up some infrastructure for use going forward,
e.g an area to commit code etc and an issue tracker to raise items.

In keeping with prior discussion of making the project structure more
component-based, a couple of things we would like to do:

- Create an area in svn, located alongside the proton directory, e.g:
http://svn.apache.org/repos/asf/qpid/jms

- Request creation of a JIRA project, e.g QPIDJMS, inititally for use
relating to the new client but perhaps eventually serving for all QPID JMS
related components.

The latter one will require a vote for infra, which I will look to start in
the near future.

Regards,
Robbie

Re: Proton-based AMQP 1.0 JMS client

[Robbie Gemmell <ro...@gmail.com>]

On 23 May 2013 16:07, Robbie Gemmell <ro...@gmail.com> wrote:

> Hi all,
>
> As most of you will be aware, we currently have a JMS client that supports
> AMQP 0-8 / 0-9 / 0-9-1 / 0-10 and a separate JMS client supporting AMQP
> 1.0, the latter of which was partly the result of prototyping work relating
> to implementing AMQP 1.0. Since then Proton has been created, in part to
> offer a means for ourselves and others integrate AMQP 1.0 into products. We
> are already using Proton-c as basis for the AMQP 1.0 support for the C++
> client and broker, but are not as yet using Proton-J within a Qpid client
> or broker (though it is being used by the ActiveMQ project).
>
> The time has come where we would like to begin working on a Proton-based
> JMS[2.0] client. I have recently spent some time with Rob Godfrey working
> through how we could approach this, putting together a very simple client
> proof of concept using Proton-J. We are now reaching the point where we
> would like to actually set up some infrastructure for use going forward,
> e.g an area to commit code etc and an issue tracker to raise items.
>
> In keeping with prior discussion of making the project structure more
> component-based, a couple of things we would like to do:
>
> - Create an area in svn, located alongside the proton directory, e.g:
> http://svn.apache.org/repos/asf/qpid/jms
>
> - Request creation of a JIRA project, e.g QPIDJMS, inititally for use
> relating to the new client but perhaps eventually serving for all QPID JMS
> related components.
>
> The latter one will require a vote for infra, which I will look to start
> in the near future.
>
> Regards,
> Robbie
>

I have now opened a vote regarding creation of a QPIDJMS JIRA project as
mentioned above. I would encourage committers to vote even if you are
unlikely to be contributing to the related component(s).

Re: Proton-based AMQP 1.0 JMS client

[Rajith Attapattu <ra...@gmail.com>]

+1 for a different JIRA system.
I believe that is the only way we can support an independent release cycle.

Rajith


On Thu, May 23, 2013 at 2:36 PM, Rob Godfrey <ro...@gmail.com>wrote:

> On 23 May 2013 20:24, Justin Ross <jr...@apache.org> wrote:
>
> > This is great news!
> >
> > On Thu, May 23, 2013 at 11:07 AM, Robbie Gemmell
> > <ro...@gmail.com> wrote:
> > > Hi all,
> > [snip]
> > > In keeping with prior discussion of making the project structure more
> > > component-based, a couple of things we would like to do:
> > >
> > > - Create an area in svn, located alongside the proton directory, e.g:
> > > http://svn.apache.org/repos/asf/qpid/jms
> >
> > Perfect, IMO.
> >
> > > - Request creation of a JIRA project, e.g QPIDJMS, inititally for use
> > > relating to the new client but perhaps eventually serving for all QPID
> > JMS
> > > related components.
> >
> > Out of curiosity, why do you suggest a distinct jira instance (versus
> > using a jira component)?  I don't have a strong preference either way.
> >
>
> So for me there's a couple of reasons.  Most importantly the existing JIRA
> system is full of JIRAs for the existing client(s) which will make it very
> difficult to distinguish JIRAs for the new component from JIRAs relating to
> the older client libraries.  Within the context of a "QPID" JIRA system
> trying define components for "JMS client for AMQP 0-8/9/10", "JMS client
> for AMQP 1-0 not build on proton", and "JMS AMQP 1-0 client based on
> proton" such that people don't get confused may be difficult.  Secondly
> we'll definitely be using a different release schedule / version numbering
> from the existing components.  Once we sort out the components better I'd
> be fine with moving the older clients into the QPIDJMS jira/directory and
> we can tailor the component names to reduce any likelihood of confusion.
>
> -- Rob
>
>
> >
> > Justin
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
> > For additional commands, e-mail: dev-help@qpid.apache.org
> >
> >
>

Re: Proton-based AMQP 1.0 JMS client

[Rob Godfrey <ro...@gmail.com>]

On 23 May 2013 20:24, Justin Ross <jr...@apache.org> wrote:

> This is great news!
>
> On Thu, May 23, 2013 at 11:07 AM, Robbie Gemmell
> <ro...@gmail.com> wrote:
> > Hi all,
> [snip]
> > In keeping with prior discussion of making the project structure more
> > component-based, a couple of things we would like to do:
> >
> > - Create an area in svn, located alongside the proton directory, e.g:
> > http://svn.apache.org/repos/asf/qpid/jms
>
> Perfect, IMO.
>
> > - Request creation of a JIRA project, e.g QPIDJMS, inititally for use
> > relating to the new client but perhaps eventually serving for all QPID
> JMS
> > related components.
>
> Out of curiosity, why do you suggest a distinct jira instance (versus
> using a jira component)?  I don't have a strong preference either way.
>

So for me there's a couple of reasons.  Most importantly the existing JIRA
system is full of JIRAs for the existing client(s) which will make it very
difficult to distinguish JIRAs for the new component from JIRAs relating to
the older client libraries.  Within the context of a "QPID" JIRA system
trying define components for "JMS client for AMQP 0-8/9/10", "JMS client
for AMQP 1-0 not build on proton", and "JMS AMQP 1-0 client based on
proton" such that people don't get confused may be difficult.  Secondly
we'll definitely be using a different release schedule / version numbering
from the existing components.  Once we sort out the components better I'd
be fine with moving the older clients into the QPIDJMS jira/directory and
we can tailor the component names to reduce any likelihood of confusion.

-- Rob


>
> Justin
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
> For additional commands, e-mail: dev-help@qpid.apache.org
>
>

Re: Proton-based AMQP 1.0 JMS client

[Justin Ross <jr...@apache.org>]

This is great news!

On Thu, May 23, 2013 at 11:07 AM, Robbie Gemmell
<ro...@gmail.com> wrote:
> Hi all,
[snip]
> In keeping with prior discussion of making the project structure more
> component-based, a couple of things we would like to do:
>
> - Create an area in svn, located alongside the proton directory, e.g:
> http://svn.apache.org/repos/asf/qpid/jms

Perfect, IMO.

> - Request creation of a JIRA project, e.g QPIDJMS, inititally for use
> relating to the new client but perhaps eventually serving for all QPID JMS
> related components.

Out of curiosity, why do you suggest a distinct jira instance (versus
using a jira component)?  I don't have a strong preference either way.

Justin

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org