to implement a STOMP consumer, you just have to listen to Stomp MESSAGE frames on the socket after you client is authenticated.
StompConnection, StompFrame, etc. are HornetQ internal classes and are not meant to be used on the client side.
Hi Jeff, thanks for the answer
So i only need to get an input stream from the socket and perform read operations in the same port i used to send the message?
You are right, of course ... i was able to capture the CONNECTED response, and i expect be able to capture all other responses.
However i wonder if there is any restriction about the size of the message ... related connection timeout, stomp specific restrictions, or something like that,