Details

    • Type: Improvement Improvement
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 1.1
    • Fix Version/s: None
    • Labels:
      None

      Description

      Just like with AMQP in JMS_SPEC-9, the STOMP protocol should be taken into consideration in the next release of the spec.

      It should continue to be a goal of this specification, though, to make it easier to implement the API on top of whatever wire protocol is chosen by the vendor.

        Activity

        Hide
        abien added a comment -

        Could you please be more precise? JMS is just an API, not a wire protocol. Could you give a concrete example?

        But :+1 for every JMS-API change which would improve interoperability with STOMP or any other relevant messaging product.

        Show
        abien added a comment - Could you please be more precise? JMS is just an API, not a wire protocol. Could you give a concrete example? But :+1 for every JMS-API change which would improve interoperability with STOMP or any other relevant messaging product.
        Hide
        Nigel Deakin added a comment -

        This needs some specific proposals.

        This general topic will be raised with the expert group for possible inclusion in the JMS 2.0 public draft. Tagging accordingly.

        Show
        Nigel Deakin added a comment - This needs some specific proposals. This general topic will be raised with the expert group for possible inclusion in the JMS 2.0 public draft. Tagging accordingly.
        Hide
        fribeiro added a comment -

        You may want to go ahead and close the issue.

        Show
        fribeiro added a comment - You may want to go ahead and close the issue.

          People

          • Assignee:
            Unassigned
            Reporter:
            fribeiro
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated: