[Jboss-dev-forums] [Design of EJB 3.0] - using MC beanfactory for configuration

[<bil...@jb...>]

We need to finally think about how we are going to replace standardjboss.xml from the old EJB 2.1 container.  One thought that comes to mind is that we define Microcontainer BeanFactories in XML for each container type.  We want this standardjboss.xml replacement to be as generic as possible.

We do already have the notion of an AOP AspectDomain, but this is really not good enough as we will want to inject things into the EJBContainer like the Timerservice that is being used, the MBeanServer, TM, etc...  We also need the ability to define default ActivationSpecs and things like that.  With the AspectDomain, you *can* overload/define new annotations in XML, but we need the ability to define generically other configuration items.

There has been some work in MC land with JBoss AOP integration.  So I'm thinking that one beanfactory definition in XML would also include the aspect domain definition for the template for that type of EJB Container.

So, we have to think of how this all wires together.  We may need two different beanfactories.  One for creating EJBContainers, the other for instantiating EJB instances themselves.  The user may want to define their own injections/configuration for EJB instances.  For the EJB instances, we may want to extend the jboss.xml schema to allow the extension and definition of a beanfactory for the EJB.

Hope this makes sense, let's think and discuss more.

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

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