Suggestions for JMS Queue and Topic naming conventions

Question

For larger JMS deployments what are your best practice suggestions for naming conventions?

Currently we're following the suggestions in the Sun Developer Network Blueprints. For example:

jms/<resource-name>[Queue|Topic]

I am concerned about scaling this as we get more and more queues and topics in the system. I'm particularly interested in hearing about experiences using hierarchical naming and how people have decided upon their naming conventions.

Answer 1

I would suggest something that incorporates corporate group, application and version information into a namespace hierarchy.

For example: jms/mygroup.myproject.version.resource.queue

This is useful if you have disparate technical groups using the same jms server cluster. Also it prevents "crosstalk" between different versions of the same application.