activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Justin Bertram (JIRA)" <>
Subject [jira] [Commented] (ARTEMIS-1695) Improve Stomp backwards compatibility with 5.x
Date Sat, 17 Mar 2018 03:54:00 GMT


Justin Bertram commented on ARTEMIS-1695:

This JIRA has already been resolved as part of 2.5.0 (which has already passed the release
vote and will be available on the website soon).  I recommend you open a new JIRA with a full
description of the functionality you're looking for (ideally with a link to the corresponding
5.x documentation).  As always, contributions are welcome!

> Improve Stomp backwards compatibility with 5.x
> ----------------------------------------------
>                 Key: ARTEMIS-1695
>                 URL:
>             Project: ActiveMQ Artemis
>          Issue Type: Improvement
>          Components: Broker, STOMP
>    Affects Versions: 2.4.0
>            Reporter: Christopher L. Shannon
>            Assignee: Christopher L. Shannon
>            Priority: Major
>             Fix For: 2.5.0
> As I was testing out STOMP in Artemis vs ActiveMQ 5.x I found a few improvements to make:
>  # ActiveMQ 5.x uses the header named "activemq.subscriptionName" for supplying a subscription
name.  We should support that as well so clients don't need to change their code. 
>  # Artemis doesn't create a session until the first message is published or a subscription
is created.  I think we should create a session on connection after authentication is complete.
 This is more in line with how CORE works and also when 5.x creates a session for a STOMP
>  # The Version 10 StompFrameHandler does not properly set the response to disconnect
if there is an authentication error.
> Also in ActiveMQ 5.x the prefixes "/topic/" and "/queue/" are used by default but this
can already be configured by setting prefixes in Artemis so we don't need to worry about that.

This message was sent by Atlassian JIRA

View raw message