[
https://issues.apache.org/jira/browse/AMQ-5889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14630513#comment-14630513
]
Christopher L. Shannon commented on AMQ-5889:
---------------------------------------------
Thanks for the pointers Tim.
That makes sense to not change the default behavior. Changing existing
functionality or introducing a bug would definitely annoy people. Probably
better to just use a new transport name like "auto" for now. We could always
enable it on the legacy transports later.
For your second point, I've actually been thinking about ways to handle that
already. I figure I could do something where I have a new prefix (such as
stompWireFormat) or just leave it as is but only apply the option if it exists.
I'd have to test out a few options and see what works best.
Handling the missing jar is pretty straight forward. All of the wire format
factories will be instantiated dynamically using reflection anyways so I can
just detect a ClassNotFoundException and return a useful error to the client if
they try and connect using an unsupported protocol.
> Support a single port for all wire protocols
> --------------------------------------------
>
> Key: AMQ-5889
> URL: https://issues.apache.org/jira/browse/AMQ-5889
> Project: ActiveMQ
> Issue Type: New Feature
> Components: Broker
> Affects Versions: 5.11.1
> Reporter: Christopher L. Shannon
>
> Both Apollo and Artemis support the ability to use a single port for all
> protocols and to have automatic detection for the protocol being used. It
> would be nice to be able to support at least a subset of this feature in the
> 5.x broker as well.
> Ideally we should at least be able to detect OpenWire, MQTT, STOMP, and AMQP
> over a TCP, SSL, and NIO transport. Websockets and HTTP would be a bonus but
> could be more difficult to implement depending on how this could work with
> Jetty so that would take some investigation.
> This is especially useful in environments where having to open up several new
> ports can be difficult because of firewall and security restrictions.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
