[ https://issues.apache.org/activemq/browse/AMQ-947?page=all ]
Rob Lugt updated AMQ-947:
-------------------------
Attachment: AMQ-947.diff
The attached patch create a file called Util\URISupport which performs a
similar function to the Java client equivalent.
The URISupport class can extract parameters from a URI query into a string map
(containing name/value pairs), which can then be used to set public properties
on any .Net class.
> Imporve .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
> 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
