activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jim Gomes (JIRA)" <jira+amq...@apache.org>
Subject [jira] Commented: (AMQNET-304) Allow compression when explicitly instantiating ActiveMQ messages
Date Tue, 11 Jan 2011 17:43:53 GMT

    [ https://issues.apache.org/jira/browse/AMQNET-304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12980206#action_12980206
] 

Jim Gomes commented on AMQNET-304:
----------------------------------

I agree with Tim's comments on not supporting this use case.

> Allow compression when explicitly instantiating ActiveMQ messages
> -----------------------------------------------------------------
>
>                 Key: AMQNET-304
>                 URL: https://issues.apache.org/jira/browse/AMQNET-304
>             Project: ActiveMQ .Net
>          Issue Type: Improvement
>          Components: NMS
>         Environment: Win7
>            Reporter: Mark Gellings
>            Assignee: Timothy Bish
>            Priority: Minor
>             Fix For: 1.5.0
>
>
> When using NMS ActiveMQ provider if one explicitly instantiates an ActiveMQTextMessage
you must set the Connection on it explicitly in order for compression to work.  This is because
when sending the message the UseCompression property is set on the Connection and the Connection
is null unless set explicitly.
> Generating an ActiveMQTextMessage off of a Session sets the Connection appropriately.
 Consider setting the Connection when the producer sends the message so that compression kicks
in if the Connection says to UseCompression, if one instantiates his own ActiveMQTextMessage
instead of creating it through the Session object.

-- 
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