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/09/29 15:28:25 UTC
[jira] Created: (AMQ-947) Imporve .Net client to accept URI
configuration parameters for connection, consumer and producer
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.
[jira] Updated: (AMQ-947) Improve .Net client to accept URI
configuration parameters for connection, consumer and producer
Posted by "Rob Lugt (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-947?page=all ]
Rob Lugt updated AMQ-947:
-------------------------
Summary: Improve .Net client to accept URI configuration parameters for connection, consumer and producer (was: Imporve .Net client to accept URI configuration parameters for connection, consumer and producer)
> 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
> 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
[jira] Commented: (AMQ-947) Improve .Net client to accept URI
configuration parameters for connection, consumer and producer
Posted by "Rob Lugt (JIRA)" <ji...@apache.org>.
[ 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
[jira] Commented: (AMQ-947) Imporve .Net client to accept URI
configuration parameters for connection, consumer and producer
Posted by "james strachan (JIRA)" <ji...@apache.org>.
[ 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
[jira] Commented: (AMQ-947) Imporve .Net client to accept URI
configuration parameters for connection, consumer and producer
Posted by "Rob Lugt (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-947?page=comments#action_37048 ]
Rob Lugt commented on AMQ-947:
------------------------------
Fab, thanks.
> 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
>
> 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
[jira] Work started: (AMQ-947) Imporve .Net client to accept URI
configuration parameters for connection, consumer and producer
Posted by "Rob Lugt (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-947?page=all ]
Work on AMQ-947 started by Rob Lugt.
> 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
>
> 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
[jira] Updated: (AMQ-947) Imporve .Net client to accept URI
configuration parameters for connection, consumer and producer
Posted by "Rob Lugt (JIRA)" <ji...@apache.org>.
[ 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
[jira] Resolved: (AMQ-947) Improve .Net client to accept URI
configuration parameters for connection, consumer and producer
Posted by "james strachan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-947?page=all ]
james strachan resolved AMQ-947.
--------------------------------
Fix Version/s: 4.1
Resolution: Fixed
Patch applied Rob - many thanks!
> 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
[jira] Commented: (AMQ-947) Imporve .Net client to accept URI
configuration parameters for connection, consumer and producer
Posted by "james strachan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-947?page=comments#action_37047 ]
james strachan commented on AMQ-947:
------------------------------------
Who-hoo!! BTW you should now have sufficient JIRA karma to assign issues to yourself or edit issues if you like 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
[jira] Assigned: (AMQ-947) Imporve .Net client to accept URI
configuration parameters for connection, consumer and producer
Posted by "Rob Lugt (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-947?page=all ]
Rob Lugt reassigned AMQ-947:
----------------------------
Assignee: Rob Lugt
> 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
>
> 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