[ 
https://issues.apache.org/activemq/browse/AMQ-2098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Timothy Bish resolved AMQ-2098.
-------------------------------

    Resolution: Fixed

Applied the supplied patch, with some additional modifications:

I added some new transformations to the set of XML and JSON transformations so 
that clients like NMS.Stomp that don't support json can also receive the 
advisory messages in a format they can digest, namely XML.  The new 
transformations are 'jms-advisory-xml' and 'jms-advisory-json'.  By default the 
advisories got out in JSON in keeping with the supplied patch.  I also added 
two top level transformation for NMS.Stomp to use since it can handle all the 
transformation types in XML, these are 'jms-xml' and 'jms-json', when these are 
supplied any Advisory Message, MapMessage or ObjectMessage is encoded into xml 
or json respectively.  

Added several additional unit tests for my changes along with the ones supplied 
in the patch.

> Advisory messages are empty when received with a Stomp subscription
> -------------------------------------------------------------------
>
>                 Key: AMQ-2098
>                 URL: https://issues.apache.org/activemq/browse/AMQ-2098
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Transport
>    Affects Versions: 5.2.0
>         Environment: ActiveMQ 5.2, Sun Java 1.6.0_11, Fedora Linux
>            Reporter: Uwe Kubosch
>            Assignee: Timothy Bish
>             Fix For: 5.4.0
>
>         Attachments: stomp-advisory.patch
>
>
> We need advisory messages for client connections, and we are stomp when 
> connecting to ActiveMQ.  When we subscribe to ActiveMQ.Advisory.Connection, 
> we get messages when clients connect of disconnect, but the messages are 
> empty.  I suspect the information is lost when converting the ActiveMQMessage 
> to a Stomp message.
> Some sort of simple serialization (like key: value pairs) of the 
> ConnectionInfo object in ActiveMQMessage.getDataStructure would solve the 
> problem.

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

Reply via email to