[Jboss-dev-forums] [Design of the JBoss EJB Container] - Re: MDB pooling - JBAS-2047

[genman <do-...@jb...>]

Okay, I think I see how this can work.

Here's the general call flow.

org.jboss.ejb.MessageDrivenContainer.internalInvoke calls its first interceptor. The invocation would need to include the MDB container configuration. This must provide enough object references and general data so that a new MDB can be deployed from a template configuration. Things that might be included: DeploymentInfo, MBeanServer, BeanMetaData, ServiceControllerMBean, etc.

A new interceptor checks that onMessage is being called, and the JMS Message is examined. For this message, a special header is checked. If the POOL_ID for the message is not set, then the request is forwarded to the MDB.  If a POOL_ID is set and it doesn't exist, then a new MDB is created with a selector that matches the POOL_IDs.

To me though, it feels like selectors are the wrong method though.


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

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