Uploaded image for project: 'ActiveMQ Classic'
  1. ActiveMQ Classic
  2. AMQ-5272

Implement JSR 356 based WebSocket transport

    XMLWordPrintableJSON

Details

    • New Feature
    • Status: Closed
    • Minor
    • Resolution: Abandoned
    • None
    • None
    • None
    • None

    Description

      The present WS transport boots up an embedded Jetty instance on its own port, which does not make sense when embedding ActiveMQ in a container-hosted application.

      Although not that difficult to hack together manually, there should be a supported first-party mechanism to configure a WS Stomp/MQTT endpoint when embedded in a JSR 356 compatible container.

      Attachments

        1. StompEndpoint.java
          6 kB
          Neb Bozovic
        2. StompTransportServer.java
          3 kB
          Neb Bozovic

        Issue Links

          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. AMQ-5356 Unable to see message contents from the web UI

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved

          Activity

            People

              Unassigned Unassigned
              nbozovic Neb Bozovic
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: