It also unclear how the current AOP annotations/xml will feed into the 
configuration 
in particular with relation to dependencies.

e.g. Take an EJB2 bean getting deployed into the microcontainer.
The domain is defined not through annotations but from a mapping of jboss.xml
metadata into some bean config inside the new kernel.

jboss.xml

  | <jboss>
  |    <security-domain>MyRealm</security-domain>
  | ...
  | </jboss>
  | 

This needs to be transformed into a microcontainer configuration that
waits for MyRealm to appear in JNDI before completing the EJB container
construction.
The registry style dependency is a feature all implemented in the current
microcontainer code.

What is clear to me is that this type of thing (whether it xml or annotations)
needs to be transformed into some form of dependency injection
on a metadata object otherwise the microcontainer isn't go to know the correct
startup order:

  | <bean ...>
  |    <attribute name="Context">Security</attribute>
  |    <attribute name="Id">Id</attribute>
  |    <attribute name="Object"><depends name="MyRealm" 
type="JNDI"/></attribute>
  | 

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

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


-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to