Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Message-ID: <15427819.1172572746975.JavaMail.jira@brutus>
Date: Tue, 27 Feb 2007 02:39:06 -0800 (PST)
From: "james strachan (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Subject: [jira] Moved: (AMQNET-35) .Net Client: allow specification of
 wireFormat parameters in broker URI
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit


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

james strachan moved AMQ-989 to AMQNET-35:
------------------------------------------

        Fix Version/s:     (was: 4.1.0)
                       1.0
          Component/s:     (was: NMS (C# client))
    Affects Version/s:     (was: 4.0.2)
                  Key: AMQNET-35  (was: AMQ-989)
              Project: ActiveMQ .Net  (was: ActiveMQ)

> .Net Client: allow specification of wireFormat parameters in broker URI
> -----------------------------------------------------------------------
>
>                 Key: AMQNET-35
>                 URL: https://issues.apache.org/activemq/browse/AMQNET-35
>             Project: ActiveMQ .Net
>          Issue Type: Improvement
>         Environment: Windows
>            Reporter: Rob Lugt
>         Assigned To: james strachan
>             Fix For: 1.0
>
>         Attachments: amq989.txt
>
>
> Update required to TcpTransportFactory to accept wireFormat connection parameters in the connection URI.  This is the only means for .Net client applications to set properties such as tight/loose encoding.
> Please apply the attached patch.
> Best Regards
> Rob Lugt

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