Perhaps the name "default connection factory" is misleading. It's not so much a default connection factory as a built-in connection factory, which may be used by any Java EE application to connect to the application server's built-in JMS provider. A large proportion (probably the majority) of JMS applications in Java EE use the built-in JMS provider so this is intended to be a genuinely useful feature for real applications.
I may be misunderstanding your comment, but are you asking for a JMS provider to have a single built-in queue, and a single built-in topic? This might be something which the novice developer could use when making their first tentative experiments to learn JMS. However this would be of no use for anything more than a throw-away training exercise, since the moment you deployed more than one application their messages would start getting mixed up. I think that's too narrow a use case to be worth attempting to require as a standard feature.
On 07/11/2012 16:07, Antonio Goncalves wrote:
Nigel, sorry if this has already been debated in the JMS 2.0 EG, but why can't we also have a default Queue and a default Topic ? In development phase I would love to write something like this :
[javaee-spec users] [jsr342-experts] Re: custom injection annotations
|Yoon Kyung Koo||11/06/2012|
[javaee-spec users] Re: [jsr342-experts] Re: custom injection annotations