So any input on this? I am trying to construct a header exchange subscription using JMS. How would the destination and jndi properties look like?
Thanks On Wed, May 18, 2011 at 4:01 PM, qpid user 2 <qpid.use...@gmail.com> wrote: > Ok. Originally we thought using a native API such as Messaging API in C++ > would reduce our dependencies from JMS. > I have played with JMS one now and if thats the only one supported, I would > try using it. > > My question now, is that how can I subscribe to a header exchange using the > MessageConsumer and the Destination generated through JNDI lookup? How > should the properties look like? An example/code snippet would be much > helpful. > > Thanks > Siamak > > > > On Wed, May 18, 2011 at 9:45 AM, Rajith Attapattu <rajit...@gmail.com>wrote: > >> The C++ API you are referring to is quite similar to the JMS API. >> Capabilities wise they are the same albeit with a few differences. >> >> > How can I use native java APIs to subscribe to events? >> May I know why you think the JMS API is unable to do this ? >> Or rather what advantages you think a native API has over the JMS API ? >> >> If we understand your use cases then perhaps we can see how best we >> could support them while still using the JMS API. >> >> Regards, >> >> Rajith >> >> On Tue, May 17, 2011 at 8:25 PM, qpid user 2 <qpid.use...@gmail.com> >> wrote: >> > Hi guys, >> > >> > I am trying to use Java for retrieving events through subscription. But >> I >> > noticed there seems to be no Messaging API available in Java as in C++. >> Is >> > that through? if thats the case, what are the Sender and Receiver >> classes >> > for? >> > How can I use native java APIs to subscribe to events? Is there anyway? >> or >> > its all just JMS? If there is anyway to do so, code snippets would be >> much >> > appreciated. >> > >> > Thanks a bunch >> > >> >> --------------------------------------------------------------------- >> Apache Qpid - AMQP Messaging Implementation >> Project: http://qpid.apache.org >> Use/Interact: mailto:users-subscr...@qpid.apache.org >> >> >
