You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Rob Lugt (JIRA)" <ji...@apache.org> on 2006/10/18 11:13:17 UTC
[jira] Created: (AMQ-989) .Net Client: allow specification of
wireFormat parameters in broker URI
.Net Client: allow specification of wireFormat parameters in broker URI
-----------------------------------------------------------------------
Key: AMQ-989
URL: https://issues.apache.org/activemq/browse/AMQ-989
Project: ActiveMQ
Issue Type: Improvement
Components: NMS (C# client)
Affects Versions: 4.0.2
Environment: Windows
Reporter: Rob Lugt
Assigned To: james strachan
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.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AMQ-989) .Net Client: allow specification of
wireFormat parameters in broker URI
Posted by "Rob Lugt (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-989?page=all ]
Rob Lugt updated AMQ-989:
-------------------------
Attachment: amq989.txt
> .Net Client: allow specification of wireFormat parameters in broker URI
> -----------------------------------------------------------------------
>
> Key: AMQ-989
> URL: https://issues.apache.org/activemq/browse/AMQ-989
> Project: ActiveMQ
> Issue Type: Improvement
> Components: NMS (C# client)
> Affects Versions: 4.0.2
> Environment: Windows
> Reporter: Rob Lugt
> Assigned To: james strachan
> 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.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (AMQ-989) .Net Client: allow specification of
wireFormat parameters in broker URI
Posted by "james strachan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-989?page=all ]
james strachan resolved AMQ-989.
--------------------------------
Fix Version/s: 4.1
Resolution: Fixed
I think I've faithfully applied your patch for this issue - many thanks. This issue seemed to cut across a few other issues to do with logging; could you double check I"ve applied your patch correctly please?
> .Net Client: allow specification of wireFormat parameters in broker URI
> -----------------------------------------------------------------------
>
> Key: AMQ-989
> URL: https://issues.apache.org/activemq/browse/AMQ-989
> Project: ActiveMQ
> Issue Type: Improvement
> Components: NMS (C# client)
> Affects Versions: 4.0.2
> Environment: Windows
> Reporter: Rob Lugt
> Assigned To: james strachan
> Fix For: 4.1
>
> 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.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira