I haven't tried it, but I imagine STOMP would work quite well. I mean,
android uses HTTP browsers :)
MQTT is a good option too if you must save on the bandwidth.
Guess your app still has to deal with network connectivity issues
Depending on how many producers/consumers you have on the app, I w
Hi Christian,
What are your thoughts on using StompJms Vs. MQTT on Android to
connect to ActiveMQ?
-PC
On Tue, May 21, 2013 at 2:25 PM, Christian Posta
wrote:
> Interesting, I haven't come across trying to do websockets from Java. I'm
> guessing your messaging infrastructure won't open up a
Interesting, I haven't come across trying to do websockets from Java. I'm
guessing your messaging infrastructure won't open up a regular tcp-based
STOMP connector?
I don't think you'll find a Stomp over websockets implementation for Java
out of the box... but I don't think it would be too bad to c
Hi Christian,
Thanks for responding.
Unfortunately the server side messaging infrastructure to which we are
trying to connect only exposes Web Sockets that utilize the Stomp protocol.
How can my Java client use the JMS API to communicate with that server side
infrastructure?
Thanks,
-h
On Tue
1) you don't want to use ws:// for the client side within java.. that
transport's not implemented because it's intended for use in a WebSocket
enabled environment, ie, a browser. Just use the tcp://localhost:X where X
is the transportConnector configured to handle STOMP connections.
2) Use the Sto
