activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <jira+amq...@apache.org>
Subject [jira] Commented: (AMQNET-271) Add support for a Message Transformer to be set in NMS API
Date Mon, 16 Aug 2010 20:19:47 GMT

    [ https://issues.apache.org/activemq/browse/AMQNET-271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=61220#action_61220
] 

Timothy Bish commented on AMQNET-271:
-------------------------------------

Those names are fine.  

As for the JMS Spec discussion, you are right that that portion of Transformation is more
internal to each client, although a lot of it could be generic and implemented as an Abstract
class in NMS.Util but that's separate from this issue really, just added that as I originally
thought that I could use some of the bits from here to help implement it but not really the
crux of what I wanted to add in this issue, so just ignore that for now.

This issue is really just an attempt to support the same features as the Java client in regards
to Message Transformation, see:
http://activemq.apache.org/message-transformation.html



> Add support for a Message Transformer to be set in NMS API
> ----------------------------------------------------------
>
>                 Key: AMQNET-271
>                 URL: https://issues.apache.org/activemq/browse/AMQNET-271
>             Project: ActiveMQ .Net
>          Issue Type: Improvement
>          Components: ActiveMQ, EMS, MSMQ, NMS, Stomp
>    Affects Versions: 1.3.0
>            Reporter: Timothy Bish
>            Assignee: Timothy Bish
>            Priority: Minor
>             Fix For: 1.4.0
>
>
> Add support in the NMS API for users to set an custom MessageTransformer on the NMS object:

> IConnectionFactory
> IConnection
> ISession
> IMessageProducer
> IMessageConsumer
> The transformer would be an instance of IMessageTransformer which provides two methods:
> {noformat}
>     /// <summary>
>     /// Interface for a class that can Transform a Message from one type to another either
>     /// before consumption or before sent by a producer.
>     /// </summary>
>     public interface IMessageTransformer
>     {
>         /// <summary>
>         /// Called from an IMessageProducer prior to sending the IMessage, allows the
client
>         /// to perform a transformation on the Message prior to it being sent.  This
allows a
>         /// client to configure a single Producer to convert a Message to a format that
can be
>         /// processed by a specific receiving client.
>         /// </summary>
>         IMessage ProducerTransform(ISession session, IMessageProducer producer, IMessage
message);
>         /// <summary>
>         /// Called from an IMessageConsumer prior to dispatching the message to the client
either
>         /// by the 'Receive' methods or from the async listener event.  Allows the client
to perform
>         /// message pre-processing before some messages are dispatched into the client
code.
>         /// </summary>
>         IMessage ConsumerTransform(ISession session, IMessageConsumer producer, IMessage
message);
>     }
> {noformat}

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


Mime
View raw message