On 02/07/2011 11:55 PM, Andrew Kennedy wrote:
Perhaps we should designate a package (or more?) which will only contain public interfaces.
That sounds like a good idea to me.
Probably org.apache.qpid.jms is the right place for these?
I agree in principle, though some of the classes or interfaces already in org.apache.qpid.jms need some review in my opinion.
Pulling in definitions from other qpid packages should really be avoided for the approach you suggest (e.g. AMQShortString, ProtocolVersion, SSLConfiguration etc).
That package also includes JMS extensions. I'm not convinced that these are all features we should be encouraging people to use going forward. Certainly they are in a different category to APIs for creating implementations of standard JMS interfaces.
I am really not a fan of the connection url syntax the JMS client uses either.
--------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:[email protected]
