I am also leaning towards adding a JCA adaptor. However I'd also want to figure out if there is any merit in implementing the optional methods in JMS.
On Wed, Feb 3, 2010 at 9:15 PM, Carl Trieloff <[email protected]> wrote: > > > We should add a JCA adaptor. > > my 2 cents. > Carl. > > > > On 02/03/2010 07:53 PM, Rajith Attapattu wrote: >> >> Hi All, >> >> There have been several attempts to use Qpid JMS client within various >> containers like Application Servers, Servlet containers etc. >> However there have been a few issues around this. >> >> 1. Qpid JMS client does not implement the optional methods nor provide >> a JCA adapter >> 2. Configuration issues as system properties cannot be used when run >> in restricted environments >> >> I would like to receive feedback about the preferred approach for >> solving item 1. >> >> For the second issue we could allow as much configuration as possible >> via Connection URL, BindingURL and the new addressing syntax. >> Robert Godfrey mentioned about using JNDI for any options that doesn't >> fit into the above methods, which I think is a good solution. >> Again I would like to hear any thoughts and suggestions around this. >> >> Regards, >> >> Rajith Attapattu >> Red Hat >> http://rajith.2rlabs.com/ >> >> --------------------------------------------------------------------- >> Apache Qpid - AMQP Messaging Implementation >> Project: http://qpid.apache.org >> Use/Interact: mailto:[email protected] >> >> > > > --------------------------------------------------------------------- > Apache Qpid - AMQP Messaging Implementation > Project: http://qpid.apache.org > Use/Interact: mailto:[email protected] > > -- Regards, Rajith Attapattu Red Hat http://rajith.2rlabs.com/ --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:[email protected]
