[
https://issues.apache.org/jira/browse/AMQ-6034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14991676#comment-14991676
]
Christopher L. Shannon edited comment on AMQ-6034 at 11/5/15 1:52 PM:
----------------------------------------------------------------------
The Stomp Java support is pretty weak because the vast majority of users would
just use JMS if they were using Java. Stomp support is primarily available for
non-java clients, either through websockets or through languages like Python or
Ruby. Like Tim said, that's something that could be worked on though, and
contributions are welcome.
In regards to Stomp not being included in activemq-client.jar...that's for JMS
support and OpenWire. If you want to use Stomp in Java, you could include the
activemq-stomp.jar on your classpath and then you would have access to the
STOMP transport and StompConnection classes.
was (Author: christopher.l.shannon):
The support is pretty weak because the vast majority of users would just use
JMS if they were using Java. Stomp support is primarily available for non-java
clients, either through websockets or through languages like Python or Ruby.
Like Tim said, that's something that could be worked on though, and
contributions are welcome.
In regards to Stomp not being included in activemq-client.jar...that's for JMS
support and OpenWire. If you want to use Stomp in Java, you could include the
activemq-stomp.jar on your classpath and then you would have access to the
STOMP transport and StompConnection classes.
> The StompConnection class contains incorrect STOMP code
> -------------------------------------------------------
>
> Key: AMQ-6034
> URL: https://issues.apache.org/jira/browse/AMQ-6034
> Project: ActiveMQ
> Issue Type: Bug
> Components: stomp
> Reporter: Lionel Cons
>
> The org.apache.activemq.transport.stomp.StompConnection class contains
> incorrect code related to STOMP frame handling.
> On the receiving side, receive() uses StompWireFormat which is correct.
> However, the class also contains receiveFrame() which is not correct.
> On the sending side, most related methods use the StompFrame.format() method
> which is not correct, StompWireFormat.marshal() should be used instead.
> So, StompWireFormat should be used in all the marshal/unmarshal operations
> and equivalent code should be removed from the related classes like
> StompConnection.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
