[jboss-dev-forums] [Design of POJO Server] - Re: Implicit container dependencies

[wolfc]

"adrian at jboss.org" wrote : This has been turned off in JBoss5 (at least for EJB2).
  | 
  | 1) The code was not (is not) portable
  | 
  | 2) Just because remote access to jndi (either another member of the cluster
  | or a thirdparty jms provider) is flakey, you don't want it to create a queue
  | 
  | 3) It obscures the most common problem, which is that you mistyped the jndi name
  | 
I want this functionality. The feature is that if you're running EJB3 with JBoss Messaging, EJB3 will create a queue for you if needed.

1. We only do it when running JBoss Messaging, so it's not ment to be portable.

2. We don't stuff anything in JNDI, we ask JBoss Messaging for a queue.

It's similar to JBCTS-541, only there j2ee-mods is asking for a queue. I don't see a problem in that. Either admin, j2ee-mods or EJB3 deployer is creating a queue.

BTW. I want to get JBCTS-541 out of the way. Shall I create a new DestinationManager which hooks into ServerPeer?

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4032567#4032567

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4032567