You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Andreas Ländle (JIRA)" <ji...@apache.org> on 2010/02/08 11:19:35 UTC

[jira] Commented: (AMQ-2490) JMSXUserID not propogated to STOMP consumer

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

Andreas Ländle commented on AMQ-2490:
-------------------------------------

Is it possible to include this patch in the 5.3.1 release?
Sorry if this is a stupid question - i'm very new to the whole activemq thing and so i have very limited knowledge about activemq's release cycles and bugfix strategies.
I'm asking because i want to use ActiveMQ with the NMS Compact Framework Stomp client. Since i reckon that the devices are distributed to uncontrollable environment i depend on the fix to avoid the possibility of spoofing.

> JMSXUserID not propogated to STOMP consumer 
> --------------------------------------------
>
>                 Key: AMQ-2490
>                 URL: https://issues.apache.org/activemq/browse/AMQ-2490
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Transport
>    Affects Versions: 5.3.0
>         Environment: activemq-trunk, macosx/linux/ sun java 1.6.0
>            Reporter: James Casey
>            Assignee: Timothy Bish
>             Fix For: 5.4.0
>
>         Attachments: stomp-userid.diff
>
>
> The userID from the ActiveMQ message object is not set on a STOMP frame.
> Attached is a patch on the STOMP FrameTranslator to set a 'JMSXUserID' header if it present in the message.
> Test cases showing the header being propogated from STOMP to both JMS and STOMP consumers properly

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.