Rajith Attapattu wrote:
Currently the following are under the example folder in the JMS client. # jmsexample/ # publisher/ # pubsub/ # shared/ # simple/ # subscriber/ # transport/1. I already deleted the amqexamples folder as it contains code written against an unsupported API. 2. I am wondering what the other examples are ? On the surface some of them seems like duplicates and others I am not sure if they really belong here. 3. I suggest we align our examples with the common theme followed by the C++ and Python clients. To that end we can get rid of the current examples and write something that closely follows the C++ and Python examples. Does anybody disagree ? or have any other suggestions ?
I think it would definitely be beneficial to have examples for JMS that are explicitly constructed to be as similar as possible to parallel examples in C++ and Python.
I know what's there for Java certainly needs some work. Yesterday I had to help Ted get one of them running and the shell script that launched them was pretty abysmal. It compiles stuff in place and constructs a huge classpath via a recursive find for every jar in the tree, and this classpath ends up referencing another compiled version of the examples anyways, which means the in-place compiled version doesn't get used, and so when you modified properties or code, it has no effect.
I would certainly be in favor of killing anything similarly abysmal given a reasonable replacement.
--Rafael --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:[email protected]
