You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Rajith Attapattu (JIRA)" <qp...@incubator.apache.org> on 2010/01/18 23:54:54 UTC
[jira] Commented: (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:comment-tabpanel&focusedCommentId=12801982#action_12801982 ]
Rajith Attapattu commented on QPID-2343:
----------------------------------------
The ClientProperties.java was moved to the common module in Qpid trunk at rev 900595 as the first step.
The common module also contains code for the client, and therefore contains configuration required for the client to be accessible from within the common module. Therefore the ClientProperties.java is best be placed inside the common module.
The goal is to have a place holder for all configuration properties.
> 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
> Fix For: 0.7
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org