The JMS 1.1 spec states in section 2.3 that JMS Destinations (Queue and Topic) are administered objects for the following reason:
It is also expected there will be major differences in how a provider's system is installed and administered. If JMS clients are to be portable, they must be isolated from these proprietary aspects of a provider.
In practice however, there is often only very little information needed to create a basic Destination that is suitable for a lot of use-cases and there aren't really any major differences there. Especially if such Destinations are completely used internally in the application, they don't necessarily need to be administered objects. Many Java EE servers do make it possible to define Destinations from within the application, but every implementation has a different way to do this. This hurts portability.
JBoss AS 6.x
As can be seen in these two examples, all that the user needs to declare is a name and whether a queue or topic is required.
I would like to propose to define a standard way to define Destinations from within a Java EE application, analogous to how JDBC datasources can be defined via a DataSourceDefinition annotation and a corresponding <data-source> element in application.xml.
|Field||Original Value||New Value|
|Tags||destination javaee||destination javaee pd20-planned|
|Tags||destination javaee pd20-planned||destination javaee|
|Status||Open [ 1 ]||Resolved [ 5 ]|
|Resolution||Invalid [ 6 ]|