You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Robbie Gemmell (JIRA)" <ji...@apache.org> on 2012/09/14 17:57:07 UTC

[jira] [Resolved] (QPID-2343) Provide a consistent naming convention for JMS client properties

     [ https://issues.apache.org/jira/browse/QPID-2343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robbie Gemmell resolved QPID-2343.
----------------------------------

       Resolution: Implemented
    Fix Version/s:     (was: Future)

Resolving, this has been open for years across multiple releases and isn't receiving any specific work. Additional work can have a version-specific JIRA.
                
> Provide a consistent naming convention for JMS client properties
> ----------------------------------------------------------------
>
>                 Key: QPID-2343
>                 URL: https://issues.apache.org/jira/browse/QPID-2343
>             Project: Qpid
>          Issue Type: Improvement
>          Components: Java Client
>    Affects Versions: 0.6
>            Reporter: Rajith Attapattu
>            Assignee: Rajith Attapattu
>              Labels: possibly_complete
>         Attachments: QPID-2343.patch, QPID-2343_take2.patch
>
>
> It would be nice if all Qpid clients followed a similar convention for naming configuration properties.
> The C++ client currently use the following convention. 
> "qpid<dot><property_name>" . 
> For starters the JMS client could follow the same strategy.  Some of its properties are starting with "amqj<dot>" while other are using "qpid<dot>".
> The logical choice would be to use "qpid<dot>" with backwards compatibility for old property name.
> The following thread captured the discussion happened on qpid-dev
> http://mail-archives.apache.org/mod_mbox/qpid-dev/201001.mbox/%3Cf5f5e0731001081456g5390a9c3w95c42b6fd7a8acb3@mail.gmail.com%3E
> The following location will be used to document all the client properties.
> http://cwiki.apache.org/confluence/display/qpid/Qpid+extensions+to+AMQP
> As Robert mentioned all properties should indicate how they are used and whether they alter only client internal behaviour, or whether they are passed down the wire to the broker which could alter broker behaviour
> Later on it will be added to the documentation being developed in the Qpid svn.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org