On Mon, Sep 14, 2009 at 11:31 AM, Martin Ritchie <ritch...@apache.org> wrote:
> Are you suggesting writting a new Configuration API for the Java client? > > Have you thought how the configuration can still be performed via JNDI? I think it's important that we offer both. Being able to do this via configuration is neat, particularly if you're into IoC. > If we start having vendor specific APIs in the Java space we totally > devalue the AMQP offering IMHO. Sure it is nice to give people options > but Java users should be encoraged to stick to the JMS API, that is > until AMQP define a API which can then be adopted across all AMQP Having an AMQP API would be really good, but is probably Some Way Off for 1-0, and I don't think it will ever happen for versions before 1-0 (because nobody will put in the effort). I also think it's important for people to be able to set up their wiring through API - it's clearer what's going on and more discoverable for a start. - Aidan -- Apache Qpid - AMQP, JMS, other messaging love http://qpid.apache.org "A witty saying proves nothing" - Voltaire --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
