Hey Tom, Thank you very much for your response and help.
Tom Samplonius-2 wrote: > > > What you are doing is fairly unclear. It seems like you are trying to > use the StompConnect JMS to Stomp bridge as a JMS client. It is not a JMS > client though. StompConnect is messaging middle-ware. It presents a > Stomp protocol front-end, and translate to some other vendors JMS API. > Its main use is to still in front of another message broker's JMS API, and > convert Stomp to JMS. > I came to this realization late last night. Thank you for confirming this for me. :) Tom Samplonius-2 wrote: > > If you want to write a messaging client in Java, you should probably use > the JMS API. Take a look at: > > http://java.sun.com/products/jms/tutorial/ > > And if you are using Java, you might as well use OpenWire too. The JMS > API is pretty rich, in comparison to Stomp, so you can actually get status > like queue size too. > I will read this tutorial and try to apply it. Thank you again. Tom Samplonius-2 wrote: > > > And you should probably check the Web Console or JConsole to see if the > messages are actually in the queue you think they should be. Perhaps the > This was a point that I forgot to mention in my last message. According to JConsole my messages are there in an AMQ queue. This is also confirmed by my perl subscriber that is able to consume the messages. Tom Samplonius-2 wrote: > > > And a OpenWire consumer and a Stomp producer should be no problem. But > you should take care on your message encoding. > I am under the impression that the example java consumer ConsumerTool.java that is included in the AMQ distribution is an OpenWire consumer example, is this correct? Thanks, Ian -- View this message in context: http://www.nabble.com/Java-stomp-subscriber%2C-StompConnect--tf3984709s2354.html#a11329175 Sent from the ActiveMQ - User mailing list archive at Nabble.com.
