You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@activemq.apache.org by "Timothy Bish (JIRA)" <ji...@apache.org> on 2014/07/11 21:49:04 UTC

[jira] [Commented] (AMQ-5272) Implement JSR 356 based WebSocket transport

    [ https://issues.apache.org/jira/browse/AMQ-5272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14059257#comment-14059257 ] 

Timothy Bish commented on AMQ-5272:
-----------------------------------

Contributions are welcomed. 

> Implement JSR 356 based WebSocket transport
> -------------------------------------------
>
>                 Key: AMQ-5272
>                 URL: https://issues.apache.org/jira/browse/AMQ-5272
>             Project: ActiveMQ
>          Issue Type: New Feature
>            Reporter: Neb Bozovic
>            Priority: Minor
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.2#6252)