ActiveMQ
  1. ActiveMQ
  2. AMQ-2833

Fix to STOMP Transport fixing message type selection

    Details

    • Type: Improvement Improvement
    • Status: Resolved
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 5.4.0
    • Component/s: Transport
    • Labels:
      None
    • Environment:

      STOMP clients which always sets the content-length header in out going messages

    • Patch Info:
      Patch Available

      Description

      Ruby's STOMP client always sets the content-length header and does not provide a mechanism to override the behavior. In addition, the 1.0 STOMP specification states the content-length header is optional but recommended. I implemented the feature discussed in AMQ-739 utilizing the 'amq-msg-type' header to select the message type. I've only implemented 'text' and 'byte' message types.

        Activity

        Hide
        Mark Eschbach added a comment -

        This patch provides the describe 'amq-msg-type' feature.

        Show
        Mark Eschbach added a comment - This patch provides the describe 'amq-msg-type' feature.
        Hide
        Mark Eschbach added a comment -

        I cleared the estimated time as I misunderstood what the field would indicate.

        Show
        Mark Eschbach added a comment - I cleared the estimated time as I misunderstood what the field would indicate.
        Hide
        Rob Davies added a comment -

        Patch applied in SVN revision 965542

        Show
        Rob Davies added a comment - Patch applied in SVN revision 965542

          People

          • Assignee:
            Rob Davies
            Reporter:
            Mark Eschbach
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development