You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by Fraser Adams <fr...@blueyonder.co.uk> on 2013/03/24 08:15:11 UTC

Location for Java QMF2 code + QMF GUI

Hello all,
I'm looking to commit the Java QMF2 API, tools and GUI that I've 
hitherto had as tarballs here

https://issues.apache.org/jira/browse/QPID-3675

It's all pretty self-contained and although has dependencies on the Qpid 
Java it doesn't impact anything in the main code base.

My preference for location would be in qpid/tools/src in a new 
subdirectory java which would seem to fit in given that there's a new 
ruby subdirectory that's just been added.

Does that seem reasonable?

Regards,
Frase



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


Re: management, what should the future look like? (was Re: Location for Java QMF2 code + QMF GUI)

Posted by Rob Godfrey <ro...@gmail.com>.
On 25 March 2013 20:52, Gordon Sim <gs...@redhat.com> wrote:

> On 03/25/2013 06:32 PM, Fraser Adams wrote:
>
>> If there's strength of feeling that extras is more appropriate then
>> that's fine and I'll be OK with that, but then the location of the ruby
>> stuff seems inconsistent (I'm not knocking the ruby stuff, just trying
>> to figure the most consistent place).
>>
>
> I think you make a good case there and I certainly have no objections to
> it going under tools.
>
>
I think this is definitely tools rather than extras... Intuitively I feel
that tools is part of our supported release and extras is not (it is more
of a sandbox area).  What Fraser has been working on seem to be like
something we wish to support as a released artefact.


>  The "stand alone project" thing is interesting, there was talk of this
>> for QMF last year but it didn't sprout wings, and I guess probably
>> won't. Perhaps it might be time for a proper concerted think about
>> "management" in general. Rob looks like he might announce some stuff
>> from OASIS on AMQP management in the near future, so perhaps the time is
>> ripe to move all the management stuff into a new space to start the ball
>> rolling on that general trajectory?
>>
>
> I think it very much is a good time to start thinking about management in
> general. I'm not sure I would begin by moving the existing stuff around
> though.
>
> I think I would begin by discussing what we all individually and
> collectively want from management.
>
>
Indeed.  Obviously I am going to start by stating that I believe that Qpid
should be aiming to support (and become the de facto reference
implementation of) the AMQP 1.0 Management specification.  One outcome here
would be for the tool that Fraser has contributed to become the basis for a
generic management tool that could work across all compliant
implementations of AMQP 1.0 Management.

This can be separated into (at least) two parts: mechanism and model.
Currently the AMQP group has been focused on the mechanism - how to give
"create", "read", "update", and "delete" instructions... not on the types
of objects to be managed and the properties of those objects.  I think
there is a very strong case that this second part, the model, should be
community driven based on the use cases of providers and consumers of
messaging solutions.  I would very much like the Qpid community to be an
active part of this.

Cheers,
Rob


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

management, what should the future look like? (was Re: Location for Java QMF2 code + QMF GUI)

Posted by Gordon Sim <gs...@redhat.com>.
On 03/25/2013 06:32 PM, Fraser Adams wrote:
> If there's strength of feeling that extras is more appropriate then
> that's fine and I'll be OK with that, but then the location of the ruby
> stuff seems inconsistent (I'm not knocking the ruby stuff, just trying
> to figure the most consistent place).

I think you make a good case there and I certainly have no objections to 
it going under tools.

> The "stand alone project" thing is interesting, there was talk of this
> for QMF last year but it didn't sprout wings, and I guess probably
> won't. Perhaps it might be time for a proper concerted think about
> "management" in general. Rob looks like he might announce some stuff
> from OASIS on AMQP management in the near future, so perhaps the time is
> ripe to move all the management stuff into a new space to start the ball
> rolling on that general trajectory?

I think it very much is a good time to start thinking about management 
in general. I'm not sure I would begin by moving the existing stuff 
around though.

I think I would begin by discussing what we all individually and 
collectively want from management.

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


Re: Location for Java QMF2 code + QMF GUI

Posted by Robbie Gemmell <ro...@gmail.com>.
I'll start by saying I also welcome the work fraser has done, and given it
is one of the primary reasons he was given commit rights look forward to it
making its way onto trunk.


On 25 March 2013 20:27, Fraser Adams <fr...@blueyonder.co.uk> wrote:

> On 25/03/13 19:47, Rob Godfrey wrote:
>
>> In the meantime have you got a list of all the areas where the Java
>> Broker and C++ broker are incompatible?  I'm sure Gordon and I wouldbe
>> very interested in that and would do our utmost to try to narrow that
>> gap.
>>
>> Thanks again,
>> Rob
>>
>>  Hi Rob, I'm afraid that I haven't got a full list as yet. The good news
> is that an awful lot is pretty similar. I noted some gaps in the Session
> objects in the Java broker - IIRC I think it was linking between session,
> subscription and queue. It's a little detail but it's useful in my GUI I
> can start with a connection and navigate through session and subscription
> to queue and vice versa I can start with a queue and navigate to
> connection. I suspect that I may be the only person who actually uses this
> behaviour :-D but I've also used it in another place where I audit queues
> and if someone tries to create or connect to a queue I don't have in a
> whitelist I log the connection information. Clearly I can't do that with
> the Java broker with this little piece of linkage missing. To be fair it's
> only really 'cause the Java broker model is a work in progress and it's
> marked as "TODO".
>

That is something that was specifically considered as an end piece of
functionality, but just hasnt been implemented yet. Rob started by trying
to ensure that the HTTP interface covereed the existing JMX functionality
but the intention is definitely that it expands beyond that (and already
has, just not in this area yet, again basically due to priorities and time
constraints).

>
> The main differences that I think cause pain is in the Queue object. It
> looks like there are a lot of differences between the Queue definitions for
> the C++ and Java brokers. For starters no ring queue in the Java broker (I
> use that all the time) but other differences relate to the fact that all
> the little config options seem to be different.
>
>
Yes, the queues are the are of most difference, mainly due to different
points of implementation and probably specific requirements by particular
users of each broker over time (for example, whilst a few might actually
like it, most of the users I deal with in relation to the Java broker would
have a heart attack at the thought of ring queues hehe..and since noone has
ever really nagged us about it, its just been something that never hit the
top of any lists).


> I found a list here https://cwiki.apache.org/**
> confluence/display/qpid/Qpid+**extensions+to+AMQP<https://cwiki.apache.org/confluence/display/qpid/Qpid+extensions+to+AMQP>I don't know how complete it currently is but skimming through it it looks
> consistent with what I've noted. As you can see the bulk of the differences
> are in Queue.Declare. Clearly this also means that AddressStrings can't
> really be used interoperably between the two brokers - at least with the
> management interface it's possible to "shim" to some degree between QMF and
> the Java broker internal model to try to expose some level of commonality
> clearly that won't fix it when AddressStrings are being used.
>
> I was planning on having a go adding stuff to the Java broker
> ConfiguredObjects when I'd got the other stuff committed, but the plugin
> changes and the questions about where to put the Java QMF stuff are likely
> to delay that a little.
>
> Frase
>
>
If there is specific ideas you have, feel free to send out a mail and we
can discuss how best to do things :)

Robbie

Re: Location for Java QMF2 code + QMF GUI

Posted by Gordon Sim <gs...@redhat.com>.
On 03/26/2013 12:54 PM, Rob Godfrey wrote:
> OK... one final question... in the C++ broker, for a ring policy do
> acquired but not yet acknowledged messages (e.g. messages that are
> currently sitting in a client's prefetch buffer) count towards the limit?

Yes

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


Re: Location for Java QMF2 code + QMF GUI

Posted by Rob Godfrey <ro...@gmail.com>.
On 26 March 2013 13:49, Gordon Sim <gs...@redhat.com> wrote:

> On 03/26/2013 12:28 PM, Rob Godfrey wrote:
>
>> Many apologies for my misunderstanding...
>>
>
> No need, I can see where the confusion would arise, hence the
> clarification!
>
>
>  In this case there shouldn't be a big barrier to implementing bounded
>> queue
>> sizes in the same way in the Java Broker.
>>
>
> The question is, if you set some sort of maximum depth on a queue, what do
> you do when you hit it? You can (a) throw some error, (b) drop certain
> messages to stay within the limit, (c) something else.
>
> The 'ring' queue policy is really a policy to evict the oldest messages
> (or the lowest priority messages for a priority queue).
>
>
>  I find the "ring" name somewhat
>> confusing then as the implementation is not actually a ring but simply a
>> bounded buffer where the oldest unconsumed message is discarded when the
>> queue size hits the bound.
>>
>
> Yes, I've made a mess of naming in more than one area I'm afraid!
>
>
>  Is there any special treatment of priority queues (do you discard lower
>> priority messages in preference to higher priority), or is the aging
>> strict?
>>
>
> Priority queues discard the lowest priority messages first (choosing the
> oldest messages within the same priority level for eviction).
>
>
>
OK... one final question... in the C++ broker, for a ring policy do
acquired but not yet acknowledged messages (e.g. messages that are
currently sitting in a client's prefetch buffer) count towards the limit?
If not what happens if such messages are released by the client at a
subsequent point?

Thanks for your help,
Rob


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

Re: Location for Java QMF2 code + QMF GUI

Posted by Gordon Sim <gs...@redhat.com>.
On 03/26/2013 12:28 PM, Rob Godfrey wrote:
> Many apologies for my misunderstanding...

No need, I can see where the confusion would arise, hence the clarification!

> In this case there shouldn't be a big barrier to implementing bounded queue
> sizes in the same way in the Java Broker.

The question is, if you set some sort of maximum depth on a queue, what 
do you do when you hit it? You can (a) throw some error, (b) drop 
certain messages to stay within the limit, (c) something else.

The 'ring' queue policy is really a policy to evict the oldest messages 
(or the lowest priority messages for a priority queue).

> I find the "ring" name somewhat
> confusing then as the implementation is not actually a ring but simply a
> bounded buffer where the oldest unconsumed message is discarded when the
> queue size hits the bound.

Yes, I've made a mess of naming in more than one area I'm afraid!

> Is there any special treatment of priority queues (do you discard lower
> priority messages in preference to higher priority), or is the aging strict?

Priority queues discard the lowest priority messages first (choosing the 
oldest messages within the same priority level for eviction).


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


Re: Location for Java QMF2 code + QMF GUI

Posted by Rob Godfrey <ro...@gmail.com>.
On 26 March 2013 12:45, Gordon Sim <gs...@redhat.com> wrote:

> On 03/25/2013 10:16 PM, Rob Godfrey wrote:
>
>>   The implementation of persistence in
>> the C++ broker pretty much forced them to define ring queues.
>>
>
> Actually the introduction of ring queues was not driven by the store at
> all. It came from use cases where build up of queues beyond a given point
> was undesirable and where the older messages could be ignored in those
> cases. They effectively implement a policy of 'only keep the last N
> messages', whereas say using a TTL would be a policy of 'only keep messages
> for T seconds'.
>
>
>   That's not
>> to say that there aren't non-persistent use cases for them.  The
>> subtleties
>> are about what happens when consumption from the queue is not strictly
>> FIFO.  The C++ persistent queue implementation literally is a ring.  Thus
>> is you have non-FIFO consumption you can get "ring" overwriting even when
>> the number of unconsumed messages in the queue is less than the ring size.
>>
>
> The store will not overwrite, it will simply refuse to enqueue more if
> there is no more space (that may indeed be when there is only one message
> still enqueued, if it happens to be at the start of the 'ring'). The ring
> buffer used in the journal is entirely distinct from the ring queues in
> memory (which can for example evict out of order, based on priority).
>
>
>
Many apologies for my misunderstanding...

In this case there shouldn't be a big barrier to implementing bounded queue
sizes in the same way in the Java Broker. I find the "ring" name somewhat
confusing then as the implementation is not actually a ring but simply a
bounded buffer where the oldest unconsumed message is discarded when the
queue size hits the bound.

Is there any special treatment of priority queues (do you discard lower
priority messages in preference to higher priority), or is the aging strict?

Cheers,
Rob


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

Re: Location for Java QMF2 code + QMF GUI

Posted by Gordon Sim <gs...@redhat.com>.
On 03/25/2013 10:16 PM, Rob Godfrey wrote:
>   The implementation of persistence in
> the C++ broker pretty much forced them to define ring queues.

Actually the introduction of ring queues was not driven by the store at 
all. It came from use cases where build up of queues beyond a given 
point was undesirable and where the older messages could be ignored in 
those cases. They effectively implement a policy of 'only keep the last 
N messages', whereas say using a TTL would be a policy of 'only keep 
messages for T seconds'.

>  That's not
> to say that there aren't non-persistent use cases for them.  The subtleties
> are about what happens when consumption from the queue is not strictly
> FIFO.  The C++ persistent queue implementation literally is a ring.  Thus
> is you have non-FIFO consumption you can get "ring" overwriting even when
> the number of unconsumed messages in the queue is less than the ring size.

The store will not overwrite, it will simply refuse to enqueue more if 
there is no more space (that may indeed be when there is only one 
message still enqueued, if it happens to be at the start of the 'ring'). 
The ring buffer used in the journal is entirely distinct from the ring 
queues in memory (which can for example evict out of order, based on 
priority).

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


Re: Location for Java QMF2 code + QMF GUI

Posted by Rob Godfrey <ro...@gmail.com>.
On 25 March 2013 23:05, Fraser Adams <fr...@blueyonder.co.uk> wrote:

> On 25/03/13 20:38, Rob Godfrey wrote:
>
>>
>> We should definitely try to address the cases where queue arguments simply
>> have different names.  Things like ring queues are a little odd.  In the
>> C++ broker they make a lot of sense because of the design of the
>> persistent
>> store in use.
>>
> I'm not sure that it's just because of the design of the persistent store
> where ring queues make sense. I'm responsible for a large federated
> topology of C++ brokers and we use ring queues pretty much everywhere
> (without persistence).
>
>
Sorry - I should have been clearer... The implementation of persistence in
the C++ broker pretty much forced them to define ring queues.  That's not
to say that there aren't non-persistent use cases for them.  The subtleties
are about what happens when consumption from the queue is not strictly
FIFO.  The C++ persistent queue implementation literally is a ring.  Thus
is you have non-FIFO consumption you can get "ring" overwriting even when
the number of unconsumed messages in the queue is less than the ring size.

The Java Broker doesn't have that sort of implementation.  The in-memory
queues are just (fancy) linked lists... and the disk storage is just a
transaction log.  As such it'd actually be quite hard to mimic exactly the
behaviour of the C++ queue.  If, OTOH, the actual requirement is just to
bound the unconsumed messages in a queue, that could certainly be
implemented as a policy.


> We need a bounded buffer architecture so we erm rejected reject policy and
> are running at very high throughput so want to avoid the performance hit of
> persistence and our producers are real time components so we certainly
> don't want to use flow control to "push back" on the producers.
>
> It might be a fairly "specialised" set of requirements, but I've certainly
> found ring queues to be really useful indeed in our system and would have
> balked (ha ha) had I not had the option of using them.
>
>
>
>    Because the design of the store in the Java Broker is so
>> different it makes less sense to implement them in the same way... but
>> having some sort of size bounded queue would make sense... and we should
>> aim to provide a single name for this so they can be created consistently
>> across the two implementations.
>>
>>
>>  The impression that I got about the Java broker queues is that it wasn't
> possible to specify a queue size per se but to implement "bounded"
> behaviour by the use of flow control, so when the number of messages/bytes
> hits a given limit the producer gets throttled. The C++ broker has added
> flow control from I think 0.12 - though I think the parameters for that are
> messages but the Java broker limits are in bytes (aaaarrrrggghhh).
>
>
Yeah - this is driven by the fact that the user requirement we were meeting
was about not running out of memory so bytes makes more sense as the value
to limit.  Adding a count limit would not be too hard.  As above also
implementing some sort of discard policy based on bounding the number of
unconsumed messages in a queue is not that hard either.  It just wouldn't
be quite the same as the C++ ring queue.


> None of this is really insurmountable, but getting the little things right
> I think will ultimately make a big difference.
>
> From a user perspective some of this comes across rather as "black magic"
> the confluence wiki page that you put together describing some of the
> differences isn't exactly easy to find (I found it by accident and
> bookmarked it :-))
>
>
Yeah - we *really* need to sort our wiki and docs.  Having people such as
yourself who can point this out to us certainly helps :-)


> There's a bit of a common theme in my rambles isn't there :-)
>
>
Understood... Obviously any time you can spare to help us try to make
things better is much appreciated :-)

Cheers,
Rob


> Cheers,
>
> Frase
>
>
>
>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.**org<de...@qpid.apache.org>
> For additional commands, e-mail: dev-help@qpid.apache.org
>
>

Re: Location for Java QMF2 code + QMF GUI

Posted by Fraser Adams <fr...@blueyonder.co.uk>.
On 25/03/13 20:38, Rob Godfrey wrote:
>
> We should definitely try to address the cases where queue arguments simply
> have different names.  Things like ring queues are a little odd.  In the
> C++ broker they make a lot of sense because of the design of the persistent
> store in use.
I'm not sure that it's just because of the design of the persistent 
store where ring queues make sense. I'm responsible for a large 
federated topology of C++ brokers and we use ring queues pretty much 
everywhere (without persistence).

We need a bounded buffer architecture so we erm rejected reject policy 
and are running at very high throughput so want to avoid the performance 
hit of persistence and our producers are real time components so we 
certainly don't want to use flow control to "push back" on the producers.

It might be a fairly "specialised" set of requirements, but I've 
certainly found ring queues to be really useful indeed in our system and 
would have balked (ha ha) had I not had the option of using them.


>   Because the design of the store in the Java Broker is so
> different it makes less sense to implement them in the same way... but
> having some sort of size bounded queue would make sense... and we should
> aim to provide a single name for this so they can be created consistently
> across the two implementations.
>
>
The impression that I got about the Java broker queues is that it wasn't 
possible to specify a queue size per se but to implement "bounded" 
behaviour by the use of flow control, so when the number of 
messages/bytes hits a given limit the producer gets throttled. The C++ 
broker has added flow control from I think 0.12 - though I think the 
parameters for that are messages but the Java broker limits are in bytes 
(aaaarrrrggghhh).

None of this is really insurmountable, but getting the little things 
right I think will ultimately make a big difference.

 From a user perspective some of this comes across rather as "black 
magic" the confluence wiki page that you put together describing some of 
the differences isn't exactly easy to find (I found it by accident and 
bookmarked it :-))

There's a bit of a common theme in my rambles isn't there :-)

Cheers,
Frase




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


Re: Location for Java QMF2 code + QMF GUI

Posted by Rob Godfrey <ro...@gmail.com>.
On 25 March 2013 21:27, Fraser Adams <fr...@blueyonder.co.uk> wrote:

> On 25/03/13 19:47, Rob Godfrey wrote:
>
>> In the meantime have you got a list of all the areas where the Java
>> Broker and C++ broker are incompatible?  I'm sure Gordon and I wouldbe
>> very interested in that and would do our utmost to try to narrow that
>> gap.
>>
>> Thanks again,
>> Rob
>>
>>  Hi Rob, I'm afraid that I haven't got a full list as yet. The good news
> is that an awful lot is pretty similar. I noted some gaps in the Session
> objects in the Java broker - IIRC I think it was linking between session,
> subscription and queue. It's a little detail but it's useful in my GUI I
> can start with a connection and navigate through session and subscription
> to queue and vice versa I can start with a queue and navigate to
> connection. I suspect that I may be the only person who actually uses this
> behaviour :-D but I've also used it in another place where I audit queues
> and if someone tries to create or connect to a queue I don't have in a
> whitelist I log the connection information. Clearly I can't do that with
> the Java broker with this little piece of linkage missing. To be fair it's
> only really 'cause the Java broker model is a work in progress and it's
> marked as "TODO".
>
> OK - I haven't looked at the Java code for that in a while (even though
there's a fair chance that I was the guilt party who wrote it - others
(Robbie, Alex, etc) tend to be far more conscientious about these things).
Raise a JIRA if it is causing an issue, and we (I) will try to fix it
sharpish :-)


> The main differences that I think cause pain is in the Queue object. It
> looks like there are a lot of differences between the Queue definitions for
> the C++ and Java brokers. For starters no ring queue in the Java broker (I
> use that all the time) but other differences relate to the fact that all
> the little config options seem to be different.
>

I found a list here https://cwiki.apache.org/**confluence/display/qpid/Qpid+
> **extensions+to+AMQP<https://cwiki.apache.org/confluence/display/qpid/Qpid+extensions+to+AMQP>


Ah yes, I can vaguely recall creating that page a *long* time ago :-)


> I don't know how complete it currently is but skimming through it it looks
> consistent with what I've noted. As you can see the bulk of the differences
> are in Queue.Declare. Clearly this also means that AddressStrings can't
> really be used interoperably between the two brokers - at least with the
> management interface it's possible to "shim" to some degree between QMF and
> the Java broker internal model to try to expose some level of commonality
> clearly that won't fix it when AddressStrings are being used.
>
>
We should definitely try to address the cases where queue arguments simply
have different names.  Things like ring queues are a little odd.  In the
C++ broker they make a lot of sense because of the design of the persistent
store in use. Because the design of the store in the Java Broker is so
different it makes less sense to implement them in the same way... but
having some sort of size bounded queue would make sense... and we should
aim to provide a single name for this so they can be created consistently
across the two implementations.


> I was planning on having a go adding stuff to the Java broker
> ConfiguredObjects when I'd got the other stuff committed, but the plugin
> changes and the questions about where to put the Java QMF stuff are likely
> to delay that a little.
>
>
Again - apologies for this. Robbie is probably best placed to say when the
APIs are definitely "stable"... but when you check your stuff in we should
definitely make sure it is part of the Jenkins CI build so that if further
changes are made to the API we don't break the management code when we
check in such changes (or if we do we fix it ASAP).

Cheers,
Rob


> Frase
>
>
>
>
>
>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.**org<de...@qpid.apache.org>
> For additional commands, e-mail: dev-help@qpid.apache.org
>
>

Re: Location for Java QMF2 code + QMF GUI

Posted by Fraser Adams <fr...@blueyonder.co.uk>.
On 25/03/13 19:47, Rob Godfrey wrote:
> In the meantime have you got a list of all the areas where the Java
> Broker and C++ broker are incompatible?  I'm sure Gordon and I wouldbe
> very interested in that and would do our utmost to try to narrow that
> gap.
>
> Thanks again,
> Rob
>
Hi Rob, I'm afraid that I haven't got a full list as yet. The good news 
is that an awful lot is pretty similar. I noted some gaps in the Session 
objects in the Java broker - IIRC I think it was linking between 
session, subscription and queue. It's a little detail but it's useful in 
my GUI I can start with a connection and navigate through session and 
subscription to queue and vice versa I can start with a queue and 
navigate to connection. I suspect that I may be the only person who 
actually uses this behaviour :-D but I've also used it in another place 
where I audit queues and if someone tries to create or connect to a 
queue I don't have in a whitelist I log the connection information. 
Clearly I can't do that with the Java broker with this little piece of 
linkage missing. To be fair it's only really 'cause the Java broker 
model is a work in progress and it's marked as "TODO".

The main differences that I think cause pain is in the Queue object. It 
looks like there are a lot of differences between the Queue definitions 
for the C++ and Java brokers. For starters no ring queue in the Java 
broker (I use that all the time) but other differences relate to the 
fact that all the little config options seem to be different.

I found a list here 
https://cwiki.apache.org/confluence/display/qpid/Qpid+extensions+to+AMQP 
I don't know how complete it currently is but skimming through it it 
looks consistent with what I've noted. As you can see the bulk of the 
differences are in Queue.Declare. Clearly this also means that 
AddressStrings can't really be used interoperably between the two 
brokers - at least with the management interface it's possible to "shim" 
to some degree between QMF and the Java broker internal model to try to 
expose some level of commonality clearly that won't fix it when 
AddressStrings are being used.

I was planning on having a go adding stuff to the Java broker 
ConfiguredObjects when I'd got the other stuff committed, but the plugin 
changes and the questions about where to put the Java QMF stuff are 
likely to delay that a little.

Frase





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


Re: Location for Java QMF2 code + QMF GUI

Posted by Rob Godfrey <ro...@gmail.com>.
So, firstly I want to echo what Gordon has said.

Speaking for myself I am very grateful for the work you have been
doing on the QMF adapter for the Java broker.  I can only apologise
for some of the issues that you hve found in terms of
incompatibilities and I thank you for your patience in dealing with
them.

Going forward I certainly want Qpid (both the Java and C++ brokers, as
well as components coming out of the Proton workstream) to be using
the standardised AMQP 1.0 management... but while the standard is
currently focused on the mechanisms we have an opportunity as the Qpid
community to look at how type definitions and behaviours can be
standardised.  I think any such work can only benefit from starting
from the qork done in writing the QMF adapter.  I would hope that we
would be looking to adapt your GUI tool to use AMQP management as it
(AMQP management) matures (perhaps directly using AMQP over websockets
and a Proton JavaScript engine?).

In the meantime have you got a list of all the areas where the Java
Broker and C++ broker are incompatible?  I'm sure Gordon and I wouldbe
very interested in that and would do our utmost to try to narrow that
gap.

Thanks again,
Rob



On 25 March 2013 20:43, Gordon Sim <gs...@redhat.com> wrote:
> On 03/25/2013 07:25 PM, Fraser Adams wrote:
>>
>> I'd have no problem migrating things to something new (sigh!!) but I
>> really think that the QMF Management GUI I put together is pretty good
>> and I had actually just got things working so that I could talk to both
>> the C++ and Java brokers using both qpid-config and the QMF GUI, that
>> consistency seemed pretty worthwhile IMHO.
>
>
> I agree. The GUI tool was very nice and easy to use and fills a gap that no
> one else had plugged (i.e. a graphical tool for managing the c++ broker).
>
> I have yet to try out the adapter to allow the same to be used against the
> java broker, but I must say I'm impressed with your achievement there.
>
> I applaud your efforts in this area! Please do not be discouraged! The work
> you have done is very valuable now as is the insights you will now be able
> to bring to bear on future direction in this important area.
>
> --Gordon.
>
>
> ---------------------------------------------------------------------
> 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: Location for Java QMF2 code + QMF GUI

Posted by Gordon Sim <gs...@redhat.com>.
On 03/25/2013 07:25 PM, Fraser Adams wrote:
> I'd have no problem migrating things to something new (sigh!!) but I
> really think that the QMF Management GUI I put together is pretty good
> and I had actually just got things working so that I could talk to both
> the C++ and Java brokers using both qpid-config and the QMF GUI, that
> consistency seemed pretty worthwhile IMHO.

I agree. The GUI tool was very nice and easy to use and fills a gap that 
no one else had plugged (i.e. a graphical tool for managing the c++ broker).

I have yet to try out the adapter to allow the same to be used against 
the java broker, but I must say I'm impressed with your achievement there.

I applaud your efforts in this area! Please do not be discouraged! The 
work you have done is very valuable now as is the insights you will now 
be able to bring to bear on future direction in this important area.

--Gordon.

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


Re: Location for Java QMF2 code + QMF GUI

Posted by Rob Godfrey <ro...@gmail.com>.
On 25 March 2013 21:21, Rajith Attapattu <ra...@gmail.com> wrote:

> On Mon, Mar 25, 2013 at 3:25 PM, Fraser Adams
> <fr...@blueyonder.co.uk> wrote:
> > Did I tell you how much time I've expended on all this work?? :-/
> >
> >
> > it's certainly pretty discouraging. It wouldn't be so bad except that I'm
> > not aware at all of any mechanism other than QMF yet in place to control
> the
> > C++ broker and I personally feel the JMX approach on the Java broker is
> > flawed (certainly it's somewhat Java centric and at least QMF uses AMQP
> as a
> > transport).
>
> I'm really sorry. I know the feeling.
> I for one certainly value your contributions to the project and your
> perseverance and patience with us.
> As Gordon said, please don't be discouraged. I'm not saying we should
> throw away your hard work.
> It's not your fault that we are in this situation.
>
> All I want is a discussion about our management strategy and then see
> if we should commit to this path.
> We already have two brokers that have diverged quite a bit. We have a
> collection of management tools that doesn't play nice with both
> brokers.
> I'm worried about adding another to the mix given that the Java broker
> seems to have a different strategy for management.
>
>
The Java Broker is providing (albeit not quite there yet as Fase has
unfortunately discovered) a pluggable mechanism for management to allow for
JMX, HTTP and (thanks to Fraser) QMF management.  Ultimately I am looking
for all of this to be superseded by management based on standards agreed in
the AMQP technical committee, but this should (as I have said above) build
on the work that others have already done in Qpid.

The excellent work that Fraser has done is no more "wasted" (and in fact
probably much less so due to his sensible design choices) than work done in
the C++ broker on QMF.

Cheers,
Rob


> Again I apologize for this situation.
>
> Rajith
>
> > The REST approach is reasonable - as it happens the QMF stuff I've put
> > together has a REST Mapping to the QMF API, but ultimately I've become
> > pretty bugged by the lack of consistency between the two brokers and
> beyond,
> > which is something I've been trying hard to address.
> >
> > I'd have no problem migrating things to something new (sigh!!) but I
> really
> > think that the QMF Management GUI I put together is pretty good and I had
> > actually just got things working so that I could talk to both the C++ and
> > Java brokers using both qpid-config and the QMF GUI, that consistency
> seemed
> > pretty worthwhile IMHO.
> >
> > At the moment alternatives seem to be vapourware, so to my mind the real
> > disservice is leaving things in limbo.
> >
> > What I'm suggesting is actually about centralising management into it's
> own
> > area and using that to evolve towards whatever *unified* management turns
> > out to look like. There's no great reason why the existing API (plural)
> > couldn't be backed by alternate implementations as things evolve.
> Ultimately
> > both the C++ and Java brokers have pretty similar underlying internal
> > management "models" as borne out by the fact that it only took me a
> couple
> > of weekends to expose the Java stuff as a QMF Management Plugin. Unless
> > there's an intention to completely re-jig the internals a lot if this is
> > likely to be about how it is "externalised" off the broker, given that
> the
> > Java broker has just moved to a new management model is that going to
> change
> > again so soon??
> >
> >
> > It's perhaps a little unfair to single out "Java QMF" as having an
> uncertain
> > future, surely you could say the same about the python stuff (or the new
> > ruby stuff)???
> >
> > I'm more than happy to move forward once I know what trajectory that
> might
> > be, but I think that ultimately it's consistency that is really important
> > and we've got things dotted around all over the place.
> >
> > I'm just a little frustrated.
> >
> > Frase
> >
> >
> > On 25/03/13 18:50, Rajith Attapattu wrote:
> >>
> >> Actually I'd like to take a step back and ask what are our plans for
> >> QMF and management in general.
> >> Fraser, this is in no way to discourage you or devalue your current
> >> contribution.
> >> But as you rightly pointed out in the later part of your email, we
> >> should look at the bigger picture and see if we can align our selves
> >> with the AMQP working group effort.
> >>
> >>  From a community perspective, I'm not too keen to have our users to
> >> start using java QMF given the uncertain future.
> >> It might be a disservice to them.
> >> But on the positive side, your contribution has forced us to discuss
> this
> >> again!
> >>
> >> Regards,
> >>
> >> Rajith
> >>
> >> On Mon, Mar 25, 2013 at 2:32 PM, Fraser Adams
> >> <fr...@blueyonder.co.uk> wrote:
> >>>
> >>> Hi Ted,
> >>> I was torn between extras and tools. I guess what sold me on tools at
> the
> >>> moment was because I've noticed that a ruby subdirectory has just been
> >>> added
> >>> there, so having a Java one too seems to make some sense. Also as part
> of
> >>> the Java QMF stuff I've done I've striven to add ports of the
> "canonical"
> >>> python tools (such as qpid-config). Now partly that's perhaps
> >>> superfluous,
> >>> but it does provide good illustration how to use the QMF API.
> >>>
> >>> I'm a bit concerned that extras might be viewed a bit "second class
> >>> citizen"
> >>> and as I say it was the ruby stuff now in tools that swung it for me.
> >>>
> >>> If there's strength of feeling that extras is more appropriate then
> >>> that's
> >>> fine and I'll be OK with that, but then the location of the ruby stuff
> >>> seems
> >>> inconsistent (I'm not knocking the ruby stuff, just trying to figure
> the
> >>> most consistent place).
> >>>
> >>> The "stand alone project" thing is interesting, there was talk of this
> >>> for
> >>> QMF last year but it didn't sprout wings, and I guess probably won't.
> >>> Perhaps it might be time for a proper concerted think about
> "management"
> >>> in
> >>> general. Rob looks like he might announce some stuff from OASIS on AMQP
> >>> management in the near future, so perhaps the time is ripe to move all
> >>> the
> >>> management stuff into a new space to start the ball rolling on that
> >>> general
> >>> trajectory?
> >>>
> >>> I haven't made a proper start on this yet 'cause I ran into issues with
> >>> the
> >>> Java broker plugin stuff changing :-/ so I probably won't be able to
> make
> >>> progress for a week or so 'cause I'm just about to go on holiday. I'll
> >>> have
> >>> email access but no development IT, it'll be good to have a discussion
> on
> >>> management in general and what the thinking on the more "strategic"
> >>> picture
> >>> is. I think it's a good time to start this discussion, it's probably
> >>> overdue
> >>> given the divergence between the C++ and Java brokers.
> >>>
> >>> Frase
> >>>
> >>>
> >>>
> >>> On 25/03/13 12:54, Ted Ross wrote:
> >>>>
> >>>> Frase,
> >>>>
> >>>> Another possibility is qpid/extras/qmf.  That's where the Python
> >>>> implementation is.  We've used the extras directory as a place to put
> >>>> more
> >>>> layered functionality, or things that might someday become stand-alone
> >>>> projects.
> >>>>
> >>>> -Ted
> >>>>
> >>>> On 03/24/2013 03:15 AM, Fraser Adams wrote:
> >>>>>
> >>>>> Hello all,
> >>>>> I'm looking to commit the Java QMF2 API, tools and GUI that I've
> >>>>> hitherto
> >>>>> had as tarballs here
> >>>>>
> >>>>> https://issues.apache.org/jira/browse/QPID-3675
> >>>>>
> >>>>> It's all pretty self-contained and although has dependencies on the
> >>>>> Qpid
> >>>>> Java it doesn't impact anything in the main code base.
> >>>>>
> >>>>> My preference for location would be in qpid/tools/src in a new
> >>>>> subdirectory java which would seem to fit in given that there's a new
> >>>>> ruby
> >>>>> subdirectory that's just been added.
> >>>>>
> >>>>> Does that seem reasonable?
> >>>>>
> >>>>> Regards,
> >>>>> Frase
> >>>>>
> >>>>>
> >>>>>
> >>>>> ---------------------------------------------------------------------
> >>>>> 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
> >>>
> >> ---------------------------------------------------------------------
> >> 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: Location for Java QMF2 code + QMF GUI

Posted by Fraser Adams <fr...@blueyonder.co.uk>.
On 25/03/13 20:21, Rajith Attapattu wrote:
> f management tools that doesn't play nice with both
> brokers.
> I'm worried about adding another to the mix given that the Java broker
> seems to have a different strategy for management.
>
Well yes and no. From what I've seen the Java broker has a pluggable 
approach (notwithstanding changes to the plugin API, but that's largely 
by the by).

As I said previously I released a QmfManagementPlugin for the Java 
Broker the other week and had that working with both qpid-config and the 
QMF GUI and in my setup I had I mixed economy of C++ and Java brokers 
controlled from a single management GUI. To my mind that seems like 
progress.

Ultimately the main differences we some differences in the underlying 
models - but nothing that appears insurmountable given modest effort.

At that point we'd no longer have "tools that doesn't play nice with 
both brokers " and the Java, Python and Ruby stuff would all work. At 
that point it would seem sensible to move forward working through the 
strategy for AMQP 1.0

It would seem nice to move forward from some point of (at least modest) 
consistency, then we can start as we intend to carry on - with a unified 
view.

Well that's my vision anyway and that's what I've been banging on about 
on the mailing lists for a fair time.


My "day job" is more of an architecture persuasion and as I've said 
several times I've been on the receiving end of having to make choices 
between products and to be frank I've sometimes struggled to justify 
Qpid primarily because of the ad hoc management (I refer to command line 
tools as not being very "CEO friendly"). I got away with it because of 
the performance, but the bottom line is that I suspect I'm not the only 
one in that position, which is one of the reasons I wrote the GUI and 
it's the reason that I made it "mobile friendly" too 'cause nice shiny 
page transitions catch the eye of casual observers (which is often where 
company "decision makers" sit). I think getting this stuff right is just 
as important as the underlying technology if we're serious about 
promoting AMQP and Qpid and getting as wide a buy in across the 
messaging industry as possible.

Frase







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


Re: Location for Java QMF2 code + QMF GUI

Posted by Rajith Attapattu <ra...@gmail.com>.
On Mon, Mar 25, 2013 at 3:25 PM, Fraser Adams
<fr...@blueyonder.co.uk> wrote:
> Did I tell you how much time I've expended on all this work?? :-/
>
>
> it's certainly pretty discouraging. It wouldn't be so bad except that I'm
> not aware at all of any mechanism other than QMF yet in place to control the
> C++ broker and I personally feel the JMX approach on the Java broker is
> flawed (certainly it's somewhat Java centric and at least QMF uses AMQP as a
> transport).

I'm really sorry. I know the feeling.
I for one certainly value your contributions to the project and your
perseverance and patience with us.
As Gordon said, please don't be discouraged. I'm not saying we should
throw away your hard work.
It's not your fault that we are in this situation.

All I want is a discussion about our management strategy and then see
if we should commit to this path.
We already have two brokers that have diverged quite a bit. We have a
collection of management tools that doesn't play nice with both
brokers.
I'm worried about adding another to the mix given that the Java broker
seems to have a different strategy for management.

Again I apologize for this situation.

Rajith

> The REST approach is reasonable - as it happens the QMF stuff I've put
> together has a REST Mapping to the QMF API, but ultimately I've become
> pretty bugged by the lack of consistency between the two brokers and beyond,
> which is something I've been trying hard to address.
>
> I'd have no problem migrating things to something new (sigh!!) but I really
> think that the QMF Management GUI I put together is pretty good and I had
> actually just got things working so that I could talk to both the C++ and
> Java brokers using both qpid-config and the QMF GUI, that consistency seemed
> pretty worthwhile IMHO.
>
> At the moment alternatives seem to be vapourware, so to my mind the real
> disservice is leaving things in limbo.
>
> What I'm suggesting is actually about centralising management into it's own
> area and using that to evolve towards whatever *unified* management turns
> out to look like. There's no great reason why the existing API (plural)
> couldn't be backed by alternate implementations as things evolve. Ultimately
> both the C++ and Java brokers have pretty similar underlying internal
> management "models" as borne out by the fact that it only took me a couple
> of weekends to expose the Java stuff as a QMF Management Plugin. Unless
> there's an intention to completely re-jig the internals a lot if this is
> likely to be about how it is "externalised" off the broker, given that the
> Java broker has just moved to a new management model is that going to change
> again so soon??
>
>
> It's perhaps a little unfair to single out "Java QMF" as having an uncertain
> future, surely you could say the same about the python stuff (or the new
> ruby stuff)???
>
> I'm more than happy to move forward once I know what trajectory that might
> be, but I think that ultimately it's consistency that is really important
> and we've got things dotted around all over the place.
>
> I'm just a little frustrated.
>
> Frase
>
>
> On 25/03/13 18:50, Rajith Attapattu wrote:
>>
>> Actually I'd like to take a step back and ask what are our plans for
>> QMF and management in general.
>> Fraser, this is in no way to discourage you or devalue your current
>> contribution.
>> But as you rightly pointed out in the later part of your email, we
>> should look at the bigger picture and see if we can align our selves
>> with the AMQP working group effort.
>>
>>  From a community perspective, I'm not too keen to have our users to
>> start using java QMF given the uncertain future.
>> It might be a disservice to them.
>> But on the positive side, your contribution has forced us to discuss this
>> again!
>>
>> Regards,
>>
>> Rajith
>>
>> On Mon, Mar 25, 2013 at 2:32 PM, Fraser Adams
>> <fr...@blueyonder.co.uk> wrote:
>>>
>>> Hi Ted,
>>> I was torn between extras and tools. I guess what sold me on tools at the
>>> moment was because I've noticed that a ruby subdirectory has just been
>>> added
>>> there, so having a Java one too seems to make some sense. Also as part of
>>> the Java QMF stuff I've done I've striven to add ports of the "canonical"
>>> python tools (such as qpid-config). Now partly that's perhaps
>>> superfluous,
>>> but it does provide good illustration how to use the QMF API.
>>>
>>> I'm a bit concerned that extras might be viewed a bit "second class
>>> citizen"
>>> and as I say it was the ruby stuff now in tools that swung it for me.
>>>
>>> If there's strength of feeling that extras is more appropriate then
>>> that's
>>> fine and I'll be OK with that, but then the location of the ruby stuff
>>> seems
>>> inconsistent (I'm not knocking the ruby stuff, just trying to figure the
>>> most consistent place).
>>>
>>> The "stand alone project" thing is interesting, there was talk of this
>>> for
>>> QMF last year but it didn't sprout wings, and I guess probably won't.
>>> Perhaps it might be time for a proper concerted think about "management"
>>> in
>>> general. Rob looks like he might announce some stuff from OASIS on AMQP
>>> management in the near future, so perhaps the time is ripe to move all
>>> the
>>> management stuff into a new space to start the ball rolling on that
>>> general
>>> trajectory?
>>>
>>> I haven't made a proper start on this yet 'cause I ran into issues with
>>> the
>>> Java broker plugin stuff changing :-/ so I probably won't be able to make
>>> progress for a week or so 'cause I'm just about to go on holiday. I'll
>>> have
>>> email access but no development IT, it'll be good to have a discussion on
>>> management in general and what the thinking on the more "strategic"
>>> picture
>>> is. I think it's a good time to start this discussion, it's probably
>>> overdue
>>> given the divergence between the C++ and Java brokers.
>>>
>>> Frase
>>>
>>>
>>>
>>> On 25/03/13 12:54, Ted Ross wrote:
>>>>
>>>> Frase,
>>>>
>>>> Another possibility is qpid/extras/qmf.  That's where the Python
>>>> implementation is.  We've used the extras directory as a place to put
>>>> more
>>>> layered functionality, or things that might someday become stand-alone
>>>> projects.
>>>>
>>>> -Ted
>>>>
>>>> On 03/24/2013 03:15 AM, Fraser Adams wrote:
>>>>>
>>>>> Hello all,
>>>>> I'm looking to commit the Java QMF2 API, tools and GUI that I've
>>>>> hitherto
>>>>> had as tarballs here
>>>>>
>>>>> https://issues.apache.org/jira/browse/QPID-3675
>>>>>
>>>>> It's all pretty self-contained and although has dependencies on the
>>>>> Qpid
>>>>> Java it doesn't impact anything in the main code base.
>>>>>
>>>>> My preference for location would be in qpid/tools/src in a new
>>>>> subdirectory java which would seem to fit in given that there's a new
>>>>> ruby
>>>>> subdirectory that's just been added.
>>>>>
>>>>> Does that seem reasonable?
>>>>>
>>>>> Regards,
>>>>> Frase
>>>>>
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> 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
>>>
>> ---------------------------------------------------------------------
>> 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: Location for Java QMF2 code + QMF GUI

Posted by Fraser Adams <fr...@blueyonder.co.uk>.
Did I tell you how much time I've expended on all this work?? :-/


it's certainly pretty discouraging. It wouldn't be so bad except that 
I'm not aware at all of any mechanism other than QMF yet in place to 
control the C++ broker and I personally feel the JMX approach on the 
Java broker is flawed (certainly it's somewhat Java centric and at least 
QMF uses AMQP as a transport).

The REST approach is reasonable - as it happens the QMF stuff I've put 
together has a REST Mapping to the QMF API, but ultimately I've become 
pretty bugged by the lack of consistency between the two brokers and 
beyond, which is something I've been trying hard to address.

I'd have no problem migrating things to something new (sigh!!) but I 
really think that the QMF Management GUI I put together is pretty good 
and I had actually just got things working so that I could talk to both 
the C++ and Java brokers using both qpid-config and the QMF GUI, that 
consistency seemed pretty worthwhile IMHO.

At the moment alternatives seem to be vapourware, so to my mind the real 
disservice is leaving things in limbo.

What I'm suggesting is actually about centralising management into it's 
own area and using that to evolve towards whatever *unified* management 
turns out to look like. There's no great reason why the existing API 
(plural) couldn't be backed by alternate implementations as things 
evolve. Ultimately both the C++ and Java brokers have pretty similar 
underlying internal management "models" as borne out by the fact that it 
only took me a couple of weekends to expose the Java stuff as a QMF 
Management Plugin. Unless there's an intention to completely re-jig the 
internals a lot if this is likely to be about how it is "externalised" 
off the broker, given that the Java broker has just moved to a new 
management model is that going to change again so soon??


It's perhaps a little unfair to single out "Java QMF" as having an 
uncertain future, surely you could say the same about the python stuff 
(or the new ruby stuff)???

I'm more than happy to move forward once I know what trajectory that 
might be, but I think that ultimately it's consistency that is really 
important and we've got things dotted around all over the place.

I'm just a little frustrated.

Frase

On 25/03/13 18:50, Rajith Attapattu wrote:
> Actually I'd like to take a step back and ask what are our plans for
> QMF and management in general.
> Fraser, this is in no way to discourage you or devalue your current
> contribution.
> But as you rightly pointed out in the later part of your email, we
> should look at the bigger picture and see if we can align our selves
> with the AMQP working group effort.
>
>  From a community perspective, I'm not too keen to have our users to
> start using java QMF given the uncertain future.
> It might be a disservice to them.
> But on the positive side, your contribution has forced us to discuss this again!
>
> Regards,
>
> Rajith
>
> On Mon, Mar 25, 2013 at 2:32 PM, Fraser Adams
> <fr...@blueyonder.co.uk> wrote:
>> Hi Ted,
>> I was torn between extras and tools. I guess what sold me on tools at the
>> moment was because I've noticed that a ruby subdirectory has just been added
>> there, so having a Java one too seems to make some sense. Also as part of
>> the Java QMF stuff I've done I've striven to add ports of the "canonical"
>> python tools (such as qpid-config). Now partly that's perhaps superfluous,
>> but it does provide good illustration how to use the QMF API.
>>
>> I'm a bit concerned that extras might be viewed a bit "second class citizen"
>> and as I say it was the ruby stuff now in tools that swung it for me.
>>
>> If there's strength of feeling that extras is more appropriate then that's
>> fine and I'll be OK with that, but then the location of the ruby stuff seems
>> inconsistent (I'm not knocking the ruby stuff, just trying to figure the
>> most consistent place).
>>
>> The "stand alone project" thing is interesting, there was talk of this for
>> QMF last year but it didn't sprout wings, and I guess probably won't.
>> Perhaps it might be time for a proper concerted think about "management" in
>> general. Rob looks like he might announce some stuff from OASIS on AMQP
>> management in the near future, so perhaps the time is ripe to move all the
>> management stuff into a new space to start the ball rolling on that general
>> trajectory?
>>
>> I haven't made a proper start on this yet 'cause I ran into issues with the
>> Java broker plugin stuff changing :-/ so I probably won't be able to make
>> progress for a week or so 'cause I'm just about to go on holiday. I'll have
>> email access but no development IT, it'll be good to have a discussion on
>> management in general and what the thinking on the more "strategic" picture
>> is. I think it's a good time to start this discussion, it's probably overdue
>> given the divergence between the C++ and Java brokers.
>>
>> Frase
>>
>>
>>
>> On 25/03/13 12:54, Ted Ross wrote:
>>> Frase,
>>>
>>> Another possibility is qpid/extras/qmf.  That's where the Python
>>> implementation is.  We've used the extras directory as a place to put more
>>> layered functionality, or things that might someday become stand-alone
>>> projects.
>>>
>>> -Ted
>>>
>>> On 03/24/2013 03:15 AM, Fraser Adams wrote:
>>>> Hello all,
>>>> I'm looking to commit the Java QMF2 API, tools and GUI that I've hitherto
>>>> had as tarballs here
>>>>
>>>> https://issues.apache.org/jira/browse/QPID-3675
>>>>
>>>> It's all pretty self-contained and although has dependencies on the Qpid
>>>> Java it doesn't impact anything in the main code base.
>>>>
>>>> My preference for location would be in qpid/tools/src in a new
>>>> subdirectory java which would seem to fit in given that there's a new ruby
>>>> subdirectory that's just been added.
>>>>
>>>> Does that seem reasonable?
>>>>
>>>> Regards,
>>>> Frase
>>>>
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> 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
>>
> ---------------------------------------------------------------------
> 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: Location for Java QMF2 code + QMF GUI

Posted by Rafael Schloming <rh...@alum.mit.edu>.
On Mon, Mar 25, 2013 at 4:45 PM, Rob Godfrey <ro...@gmail.com>wrote:

> On 25 March 2013 21:32, Rajith Attapattu <ra...@gmail.com> wrote:
>
> > On Mon, Mar 25, 2013 at 2:50 PM, Rajith Attapattu <ra...@gmail.com>
> > wrote:
> > > Actually I'd like to take a step back and ask what are our plans for
> > > QMF and management in general.
> > > Fraser, this is in no way to discourage you or devalue your current
> > > contribution.
> > > But as you rightly pointed out in the later part of your email, we
> > > should look at the bigger picture and see if we can align our selves
> > > with the AMQP working group effort.
> > >
> > > From a community perspective, I'm not too keen to have our users to
> > > start using java QMF given the uncertain future.
> > > It might be a disservice to them.
> > > But on the positive side, your contribution has forced us to discuss
> > this again!
> >
> >
>
> To address this again.  Currently QMF is the only potential common "API"
> for managing across the two brokers.  The emergence of a standardized AMQP
> 1.0 management may mean that we can change the underlying protocol being
> used by tooling, and offer us the chance to provide tooling that works
> against a greater number of implementations... But if Fraser can get his
> code to compile against the moving goalpost that is the Java codebase, and
> check it in to the Qpid project, then I think we can quite happily say that
> we will continue to support it going forward until such point as everyone
> is happy that alternatives such as AMQP 1.0 Management completely supplant
> the QMF functionality.
>
>
> > To further explain, we introduced the Qpid Messaging API and we have a
> > whole bunch of folks using it.
> > However there seems to be question marks about the future of it given
> > the emergence of Messenger.
> >
> >
> To my knowledge there is no doubt about the Messaging API.  It is
> continuing to be supported and I believe Gordon is doing excellent work in
> adding a 1-0 back end for it.
>

+1

One of the primary goals of the messaging API was to provide users with a
seamless transition from 0-x to 1.0. There really are no question marks
about its future in this regard.

As one of the designers of both APIs I can confidently say they are quite a
bit more different than people tend to realize at this point. I think we
need to be careful not to encourage people to lump them into competition
with each other, and it's certainly inappropriate to be casually spreading
FUD about the future of the messaging API or any other qpid component.

--Rafael

Re: Location for Java QMF2 code + QMF GUI

Posted by Rob Godfrey <ro...@gmail.com>.
On 25 March 2013 21:32, Rajith Attapattu <ra...@gmail.com> wrote:

> On Mon, Mar 25, 2013 at 2:50 PM, Rajith Attapattu <ra...@gmail.com>
> wrote:
> > Actually I'd like to take a step back and ask what are our plans for
> > QMF and management in general.
> > Fraser, this is in no way to discourage you or devalue your current
> > contribution.
> > But as you rightly pointed out in the later part of your email, we
> > should look at the bigger picture and see if we can align our selves
> > with the AMQP working group effort.
> >
> > From a community perspective, I'm not too keen to have our users to
> > start using java QMF given the uncertain future.
> > It might be a disservice to them.
> > But on the positive side, your contribution has forced us to discuss
> this again!
>
>

To address this again.  Currently QMF is the only potential common "API"
for managing across the two brokers.  The emergence of a standardized AMQP
1.0 management may mean that we can change the underlying protocol being
used by tooling, and offer us the chance to provide tooling that works
against a greater number of implementations... But if Fraser can get his
code to compile against the moving goalpost that is the Java codebase, and
check it in to the Qpid project, then I think we can quite happily say that
we will continue to support it going forward until such point as everyone
is happy that alternatives such as AMQP 1.0 Management completely supplant
the QMF functionality.


> To further explain, we introduced the Qpid Messaging API and we have a
> whole bunch of folks using it.
> However there seems to be question marks about the future of it given
> the emergence of Messenger.
>
>
To my knowledge there is no doubt about the Messaging API.  It is
continuing to be supported and I believe Gordon is doing excellent work in
adding a 1-0 back end for it.


> We as a community has a duty towards our users. And it is from this
> pov that I'm not so sure about if we want to add the Java QMF
> implementation *as it is without further discussions*.
>

As someone with a strong interest in the Java Broker, I am personally happy
to sat that I want to add the Java QMF implementation.  The work in the
Java Broker to allow for such plugins was in some sense driven by the
desire to encourage such work.

-- Rob

As Rob said, your contribution could be the basis for the new
> management work. So again please don't feel discouraged.
>
> Rajith
>
> > Regards,
> >
> > Rajith
> >
> > On Mon, Mar 25, 2013 at 2:32 PM, Fraser Adams
> > <fr...@blueyonder.co.uk> wrote:
> >> Hi Ted,
> >> I was torn between extras and tools. I guess what sold me on tools at
> the
> >> moment was because I've noticed that a ruby subdirectory has just been
> added
> >> there, so having a Java one too seems to make some sense. Also as part
> of
> >> the Java QMF stuff I've done I've striven to add ports of the
> "canonical"
> >> python tools (such as qpid-config). Now partly that's perhaps
> superfluous,
> >> but it does provide good illustration how to use the QMF API.
> >>
> >> I'm a bit concerned that extras might be viewed a bit "second class
> citizen"
> >> and as I say it was the ruby stuff now in tools that swung it for me.
> >>
> >> If there's strength of feeling that extras is more appropriate then
> that's
> >> fine and I'll be OK with that, but then the location of the ruby stuff
> seems
> >> inconsistent (I'm not knocking the ruby stuff, just trying to figure the
> >> most consistent place).
> >>
> >> The "stand alone project" thing is interesting, there was talk of this
> for
> >> QMF last year but it didn't sprout wings, and I guess probably won't.
> >> Perhaps it might be time for a proper concerted think about
> "management" in
> >> general. Rob looks like he might announce some stuff from OASIS on AMQP
> >> management in the near future, so perhaps the time is ripe to move all
> the
> >> management stuff into a new space to start the ball rolling on that
> general
> >> trajectory?
> >>
> >> I haven't made a proper start on this yet 'cause I ran into issues with
> the
> >> Java broker plugin stuff changing :-/ so I probably won't be able to
> make
> >> progress for a week or so 'cause I'm just about to go on holiday. I'll
> have
> >> email access but no development IT, it'll be good to have a discussion
> on
> >> management in general and what the thinking on the more "strategic"
> picture
> >> is. I think it's a good time to start this discussion, it's probably
> overdue
> >> given the divergence between the C++ and Java brokers.
> >>
> >> Frase
> >>
> >>
> >>
> >> On 25/03/13 12:54, Ted Ross wrote:
> >>>
> >>> Frase,
> >>>
> >>> Another possibility is qpid/extras/qmf.  That's where the Python
> >>> implementation is.  We've used the extras directory as a place to put
> more
> >>> layered functionality, or things that might someday become stand-alone
> >>> projects.
> >>>
> >>> -Ted
> >>>
> >>> On 03/24/2013 03:15 AM, Fraser Adams wrote:
> >>>>
> >>>> Hello all,
> >>>> I'm looking to commit the Java QMF2 API, tools and GUI that I've
> hitherto
> >>>> had as tarballs here
> >>>>
> >>>> https://issues.apache.org/jira/browse/QPID-3675
> >>>>
> >>>> It's all pretty self-contained and although has dependencies on the
> Qpid
> >>>> Java it doesn't impact anything in the main code base.
> >>>>
> >>>> My preference for location would be in qpid/tools/src in a new
> >>>> subdirectory java which would seem to fit in given that there's a new
> ruby
> >>>> subdirectory that's just been added.
> >>>>
> >>>> Does that seem reasonable?
> >>>>
> >>>> Regards,
> >>>> Frase
> >>>>
> >>>>
> >>>>
> >>>> ---------------------------------------------------------------------
> >>>> 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
> >>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
> For additional commands, e-mail: dev-help@qpid.apache.org
>
>

Re: Location for Java QMF2 code + QMF GUI

Posted by Rajith Attapattu <ra...@gmail.com>.
On Mon, Mar 25, 2013 at 2:50 PM, Rajith Attapattu <ra...@gmail.com> wrote:
> Actually I'd like to take a step back and ask what are our plans for
> QMF and management in general.
> Fraser, this is in no way to discourage you or devalue your current
> contribution.
> But as you rightly pointed out in the later part of your email, we
> should look at the bigger picture and see if we can align our selves
> with the AMQP working group effort.
>
> From a community perspective, I'm not too keen to have our users to
> start using java QMF given the uncertain future.
> It might be a disservice to them.
> But on the positive side, your contribution has forced us to discuss this again!

To further explain, we introduced the Qpid Messaging API and we have a
whole bunch of folks using it.
However there seems to be question marks about the future of it given
the emergence of Messenger.

We as a community has a duty towards our users. And it is from this
pov that I'm not so sure about if we want to add the Java QMF
implementation *as it is without further discussions*.
As Rob said, your contribution could be the basis for the new
management work. So again please don't feel discouraged.

Rajith

> Regards,
>
> Rajith
>
> On Mon, Mar 25, 2013 at 2:32 PM, Fraser Adams
> <fr...@blueyonder.co.uk> wrote:
>> Hi Ted,
>> I was torn between extras and tools. I guess what sold me on tools at the
>> moment was because I've noticed that a ruby subdirectory has just been added
>> there, so having a Java one too seems to make some sense. Also as part of
>> the Java QMF stuff I've done I've striven to add ports of the "canonical"
>> python tools (such as qpid-config). Now partly that's perhaps superfluous,
>> but it does provide good illustration how to use the QMF API.
>>
>> I'm a bit concerned that extras might be viewed a bit "second class citizen"
>> and as I say it was the ruby stuff now in tools that swung it for me.
>>
>> If there's strength of feeling that extras is more appropriate then that's
>> fine and I'll be OK with that, but then the location of the ruby stuff seems
>> inconsistent (I'm not knocking the ruby stuff, just trying to figure the
>> most consistent place).
>>
>> The "stand alone project" thing is interesting, there was talk of this for
>> QMF last year but it didn't sprout wings, and I guess probably won't.
>> Perhaps it might be time for a proper concerted think about "management" in
>> general. Rob looks like he might announce some stuff from OASIS on AMQP
>> management in the near future, so perhaps the time is ripe to move all the
>> management stuff into a new space to start the ball rolling on that general
>> trajectory?
>>
>> I haven't made a proper start on this yet 'cause I ran into issues with the
>> Java broker plugin stuff changing :-/ so I probably won't be able to make
>> progress for a week or so 'cause I'm just about to go on holiday. I'll have
>> email access but no development IT, it'll be good to have a discussion on
>> management in general and what the thinking on the more "strategic" picture
>> is. I think it's a good time to start this discussion, it's probably overdue
>> given the divergence between the C++ and Java brokers.
>>
>> Frase
>>
>>
>>
>> On 25/03/13 12:54, Ted Ross wrote:
>>>
>>> Frase,
>>>
>>> Another possibility is qpid/extras/qmf.  That's where the Python
>>> implementation is.  We've used the extras directory as a place to put more
>>> layered functionality, or things that might someday become stand-alone
>>> projects.
>>>
>>> -Ted
>>>
>>> On 03/24/2013 03:15 AM, Fraser Adams wrote:
>>>>
>>>> Hello all,
>>>> I'm looking to commit the Java QMF2 API, tools and GUI that I've hitherto
>>>> had as tarballs here
>>>>
>>>> https://issues.apache.org/jira/browse/QPID-3675
>>>>
>>>> It's all pretty self-contained and although has dependencies on the Qpid
>>>> Java it doesn't impact anything in the main code base.
>>>>
>>>> My preference for location would be in qpid/tools/src in a new
>>>> subdirectory java which would seem to fit in given that there's a new ruby
>>>> subdirectory that's just been added.
>>>>
>>>> Does that seem reasonable?
>>>>
>>>> Regards,
>>>> Frase
>>>>
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> 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
>>

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


Re: Location for Java QMF2 code + QMF GUI

Posted by Rajith Attapattu <ra...@gmail.com>.
Actually I'd like to take a step back and ask what are our plans for
QMF and management in general.
Fraser, this is in no way to discourage you or devalue your current
contribution.
But as you rightly pointed out in the later part of your email, we
should look at the bigger picture and see if we can align our selves
with the AMQP working group effort.

>From a community perspective, I'm not too keen to have our users to
start using java QMF given the uncertain future.
It might be a disservice to them.
But on the positive side, your contribution has forced us to discuss this again!

Regards,

Rajith

On Mon, Mar 25, 2013 at 2:32 PM, Fraser Adams
<fr...@blueyonder.co.uk> wrote:
> Hi Ted,
> I was torn between extras and tools. I guess what sold me on tools at the
> moment was because I've noticed that a ruby subdirectory has just been added
> there, so having a Java one too seems to make some sense. Also as part of
> the Java QMF stuff I've done I've striven to add ports of the "canonical"
> python tools (such as qpid-config). Now partly that's perhaps superfluous,
> but it does provide good illustration how to use the QMF API.
>
> I'm a bit concerned that extras might be viewed a bit "second class citizen"
> and as I say it was the ruby stuff now in tools that swung it for me.
>
> If there's strength of feeling that extras is more appropriate then that's
> fine and I'll be OK with that, but then the location of the ruby stuff seems
> inconsistent (I'm not knocking the ruby stuff, just trying to figure the
> most consistent place).
>
> The "stand alone project" thing is interesting, there was talk of this for
> QMF last year but it didn't sprout wings, and I guess probably won't.
> Perhaps it might be time for a proper concerted think about "management" in
> general. Rob looks like he might announce some stuff from OASIS on AMQP
> management in the near future, so perhaps the time is ripe to move all the
> management stuff into a new space to start the ball rolling on that general
> trajectory?
>
> I haven't made a proper start on this yet 'cause I ran into issues with the
> Java broker plugin stuff changing :-/ so I probably won't be able to make
> progress for a week or so 'cause I'm just about to go on holiday. I'll have
> email access but no development IT, it'll be good to have a discussion on
> management in general and what the thinking on the more "strategic" picture
> is. I think it's a good time to start this discussion, it's probably overdue
> given the divergence between the C++ and Java brokers.
>
> Frase
>
>
>
> On 25/03/13 12:54, Ted Ross wrote:
>>
>> Frase,
>>
>> Another possibility is qpid/extras/qmf.  That's where the Python
>> implementation is.  We've used the extras directory as a place to put more
>> layered functionality, or things that might someday become stand-alone
>> projects.
>>
>> -Ted
>>
>> On 03/24/2013 03:15 AM, Fraser Adams wrote:
>>>
>>> Hello all,
>>> I'm looking to commit the Java QMF2 API, tools and GUI that I've hitherto
>>> had as tarballs here
>>>
>>> https://issues.apache.org/jira/browse/QPID-3675
>>>
>>> It's all pretty self-contained and although has dependencies on the Qpid
>>> Java it doesn't impact anything in the main code base.
>>>
>>> My preference for location would be in qpid/tools/src in a new
>>> subdirectory java which would seem to fit in given that there's a new ruby
>>> subdirectory that's just been added.
>>>
>>> Does that seem reasonable?
>>>
>>> Regards,
>>> Frase
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> 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
>

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


Re: Location for Java QMF2 code + QMF GUI

Posted by Fraser Adams <fr...@blueyonder.co.uk>.
Hi Ted,
I was torn between extras and tools. I guess what sold me on tools at 
the moment was because I've noticed that a ruby subdirectory has just 
been added there, so having a Java one too seems to make some sense. 
Also as part of the Java QMF stuff I've done I've striven to add ports 
of the "canonical" python tools (such as qpid-config). Now partly that's 
perhaps superfluous, but it does provide good illustration how to use 
the QMF API.

I'm a bit concerned that extras might be viewed a bit "second class 
citizen" and as I say it was the ruby stuff now in tools that swung it 
for me.

If there's strength of feeling that extras is more appropriate then 
that's fine and I'll be OK with that, but then the location of the ruby 
stuff seems inconsistent (I'm not knocking the ruby stuff, just trying 
to figure the most consistent place).

The "stand alone project" thing is interesting, there was talk of this 
for QMF last year but it didn't sprout wings, and I guess probably 
won't. Perhaps it might be time for a proper concerted think about 
"management" in general. Rob looks like he might announce some stuff 
from OASIS on AMQP management in the near future, so perhaps the time is 
ripe to move all the management stuff into a new space to start the ball 
rolling on that general trajectory?

I haven't made a proper start on this yet 'cause I ran into issues with 
the Java broker plugin stuff changing :-/ so I probably won't be able to 
make progress for a week or so 'cause I'm just about to go on holiday. 
I'll have email access but no development IT, it'll be good to have a 
discussion on management in general and what the thinking on the more 
"strategic" picture is. I think it's a good time to start this 
discussion, it's probably overdue given the divergence between the C++ 
and Java brokers.

Frase


On 25/03/13 12:54, Ted Ross wrote:
> Frase,
>
> Another possibility is qpid/extras/qmf.  That's where the Python 
> implementation is.  We've used the extras directory as a place to put 
> more layered functionality, or things that might someday become 
> stand-alone projects.
>
> -Ted
>
> On 03/24/2013 03:15 AM, Fraser Adams wrote:
>> Hello all,
>> I'm looking to commit the Java QMF2 API, tools and GUI that I've 
>> hitherto had as tarballs here
>>
>> https://issues.apache.org/jira/browse/QPID-3675
>>
>> It's all pretty self-contained and although has dependencies on the 
>> Qpid Java it doesn't impact anything in the main code base.
>>
>> My preference for location would be in qpid/tools/src in a new 
>> subdirectory java which would seem to fit in given that there's a new 
>> ruby subdirectory that's just been added.
>>
>> Does that seem reasonable?
>>
>> Regards,
>> Frase
>>
>>
>>
>> ---------------------------------------------------------------------
>> 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: Location for Java QMF2 code + QMF GUI

Posted by Ted Ross <tr...@redhat.com>.
Frase,

Another possibility is qpid/extras/qmf.  That's where the Python 
implementation is.  We've used the extras directory as a place to put 
more layered functionality, or things that might someday become 
stand-alone projects.

-Ted

On 03/24/2013 03:15 AM, Fraser Adams wrote:
> Hello all,
> I'm looking to commit the Java QMF2 API, tools and GUI that I've 
> hitherto had as tarballs here
>
> https://issues.apache.org/jira/browse/QPID-3675
>
> It's all pretty self-contained and although has dependencies on the 
> Qpid Java it doesn't impact anything in the main code base.
>
> My preference for location would be in qpid/tools/src in a new 
> subdirectory java which would seem to fit in given that there's a new 
> ruby subdirectory that's just been added.
>
> Does that seem reasonable?
>
> Regards,
> Frase
>
>
>
> ---------------------------------------------------------------------
> 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