[
https://issues.apache.org/activemq/browse/AMQNET-25?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
james strachan moved AMQ-947 to AMQNET-25:
------------------------------------------
Fix Version/s: (was: 4.1.0)
Component/s: (was: NMS (C# client))
Affects Version/s: (was: 4.x)
Key: AMQNET-25 (was: AMQ-947)
Project: ActiveMQ .Net (was: ActiveMQ)
> Improve .Net client to accept URI configuration parameters for connection,
> consumer and producer
> ------------------------------------------------------------------------------------------------
>
> Key: AMQNET-25
> URL: https://issues.apache.org/activemq/browse/AMQNET-25
> Project: ActiveMQ .Net
> Issue Type: New Feature
> 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.
-
You can reply to this email to add a comment to the issue online.
