[
https://issues.apache.org/jira/browse/AMQ-5272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15045758#comment-15045758
]
Neb Bozovic commented on AMQ-5272:
----------------------------------
Ok, I can take a stab at it when I have some spare time.
Be advised that any patch will necessarily be somewhat partial, as the small
solution presented here is only intended to handle our own STOMP requirement
(not MQTT), will not provide documentation, and will not necessarily fit neatly
into the larger conceptual/architectural framework of ActiveMQ (with which I am
less than familiar).
Will this be valuable? It was my hope that this example would illuminate the
logic and necessity and motivate the development of a fully fleshed out first
party solution along the same lines. I cannot commit to developing such a
solution myself unfortunately.
> 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)
