You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Jim Gomes (JIRA)" <ji...@apache.org> on 2008/01/04 18:27:43 UTC

[jira] Created: (AMQNET-76) Change URI parameter "jms." prefix to "connection." prefix

Change URI parameter "jms." prefix to "connection." prefix
----------------------------------------------------------

                 Key: AMQNET-76
                 URL: https://issues.apache.org/activemq/browse/AMQNET-76
             Project: ActiveMQ .Net
          Issue Type: Bug
          Components: ActiveMQ Client
            Reporter: Jim Gomes
            Assignee: James Strachan
            Priority: Minor


The connection URI takes optional parameters that help configure the connection settings.  These connection parameters are prefixed with "jms.".  For example:

tcp://localhost:61616?jms.uselogging=true

This is actually a connection setting.  To be more consistent with other URI configuration settings (e.g., consumer, producer, wireformat), this prefix should be changed to "connection."  This makes the URI more internally consistent.  The new URI format would look like:

tcp://localhost:61616?connection.uselogging=true


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Closed: (AMQNET-76) Change URI parameter "jms." prefix to "connection." prefix

Posted by "Jim Gomes (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/AMQNET-76?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jim Gomes closed AMQNET-76.
---------------------------


> Change URI parameter "jms." prefix to "connection." prefix
> ----------------------------------------------------------
>
>                 Key: AMQNET-76
>                 URL: https://issues.apache.org/activemq/browse/AMQNET-76
>             Project: ActiveMQ .Net
>          Issue Type: Bug
>          Components: ActiveMQ Client
>            Reporter: Jim Gomes
>            Assignee: James Strachan
>            Priority: Minor
>
> The connection URI takes optional parameters that help configure the connection settings.  These connection parameters are prefixed with "jms.".  For example:
> tcp://localhost:61616?jms.uselogging=true
> This is actually a connection setting.  To be more consistent with other URI configuration settings (e.g., consumer, producer, wireformat), this prefix should be changed to "connection."  This makes the URI more internally consistent.  The new URI format would look like:
> tcp://localhost:61616?connection.uselogging=true

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Resolved: (AMQNET-76) Change URI parameter "jms." prefix to "connection." prefix

Posted by "Jim Gomes (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/AMQNET-76?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jim Gomes resolved AMQNET-76.
-----------------------------

    Resolution: Fixed

> Change URI parameter "jms." prefix to "connection." prefix
> ----------------------------------------------------------
>
>                 Key: AMQNET-76
>                 URL: https://issues.apache.org/activemq/browse/AMQNET-76
>             Project: ActiveMQ .Net
>          Issue Type: Bug
>          Components: ActiveMQ Client
>            Reporter: Jim Gomes
>            Assignee: James Strachan
>            Priority: Minor
>
> The connection URI takes optional parameters that help configure the connection settings.  These connection parameters are prefixed with "jms.".  For example:
> tcp://localhost:61616?jms.uselogging=true
> This is actually a connection setting.  To be more consistent with other URI configuration settings (e.g., consumer, producer, wireformat), this prefix should be changed to "connection."  This makes the URI more internally consistent.  The new URI format would look like:
> tcp://localhost:61616?connection.uselogging=true

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.