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

Implement JSR 356 based WebSocket transport

VotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    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

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

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

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment