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/11/09 01:00:05 UTC

[jira] Commented: (AMQ-947) Improve .Net client to accept URI configuration parameters for connection, consumer and producer

    [ https://issues.apache.org/activemq/browse/AMQ-947?page=comments#action_37383 ] 
            
Rob Lugt commented on AMQ-947:
------------------------------


   [[ Old comment, sent by email on Tue, 3 Oct 2006 12:52:57 +0100 ]]

Hi James

Thanks for applying the patch.  On checking the results I noticed that 
CreateProducerInfo() contains a duplicate line:

  answer.Destination = ActiveMQDestination.Transform(destination);

I guess this is a result of my patch. Could you do the honours and correct 
it?

Thanks and regards
~Rob



> Improve .Net client to accept URI configuration parameters for connection, consumer and producer
> ------------------------------------------------------------------------------------------------
>
>                 Key: AMQ-947
>                 URL: https://issues.apache.org/activemq/browse/AMQ-947
>             Project: ActiveMQ
>          Issue Type: New Feature
>          Components: NMS (C# client)
>    Affects Versions: 4.x
>            Reporter: Rob Lugt
>         Assigned To: Rob Lugt
>             Fix For: 4.1
>
>         Attachments: AMQ-947.diff
>
>
> The Java client accepts optional parameters on broker and destination URIs, which allows client programs to configure the client using the standard JMS interface.  The .Net client does not currently support parameters (it silently ignores them), but this is not made clear in the documentation.
> URI parameters are a powerful mechanism which should ideally be rolled out to all clients, but as this is client specific this Jira covers the .Net client only.
> Idelly the same URI configuration parameters should be used for both the Java and .Net clients.  The Java mechanism is based on introspection, so the .Net client should ideally use a similar mechanism.

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