You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "james strachan (JIRA)" <ji...@apache.org> on 2006/09/29 17:12:24 UTC

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

    [ https://issues.apache.org/activemq/browse/AMQ-947?page=comments#action_37044 ] 
            
james strachan commented on AMQ-947:
------------------------------------

Sounds fine with me. The main thing holding us back on this is figuring out the right .Net way to do this...

http://incubator.apache.org/activemq/maven/activemq-core/xref/org/apache/activemq/util/IntrospectionSupport.html

I wonder any chance you could try create an introspection/reflection helper class something like that so we could wire in a similar introspection URI handler to the connection / consumer / transport / socket stuff etc?

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

        

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

Posted by Rob Lugt <ro...@cheynecapital.com>.

JIRA jira@apache.org wrote:
> 
>     [
> https://issues.apache.org/activemq/browse/AMQ-947?page=comments#action_37044
> ] 
>             
> james strachan commented on AMQ-947:
> ------------------------------------
> 
> Sounds fine with me. The main thing holding us back on this is figuring
> out the right .Net way to do this...
> 
> http://incubator.apache.org/activemq/maven/activemq-core/xref/org/apache/activemq/util/IntrospectionSupport.html
> 
> I wonder any chance you could try create an introspection/reflection
> helper class something like that so we could wire in a similar
> introspection URI handler to the connection / consumer / transport /
> socket stuff etc?
> 
> 

Have done just that; patch to follow shortly.
-- 
View this message in context: http://www.nabble.com/-jira--Created%3A-%28AMQ-947%29-Imporve-.Net-client-to-accept-URI-configuration-parameters-for-connection%2C-consumer-and-producer-tf2356904.html#a6568072
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.