[
https://issues.apache.org/jira/browse/AMQ-5272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15045726#comment-15045726
]
Christopher L. Shannon commented on AMQ-5272:
---------------------------------------------
Thanks for the clarification. We gladly take contributions so if you want to
take the code you wrote and create a pull request or patch file against the
latest in master we can take a look at merging it.
> 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
> Attachments: StompEndpoint.java, StompTransportServer.java
>
>
> 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.3.4#6332)
