[QPID-2343] Provide a consistent naming convention for JMS client properties

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Implemented
• Affects Version/s: 0.6
• Component/s: JMS AMQP 0-x
• Labels: possibly_complete
• Assignee: Rajith Muditha Attapattu
• Reporter: Rajith Muditha Attapattu
• Created: 18/Jan/10 22:43
• Updated: 14/Sep/12 15:56
• Resolved: 14/Sep/12 15:56

Description

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/[e-mail]%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.