Think of the DynamicBean as a generic factory.  You configure the aspect as 
follows:


  | <aspect class="org.jboss.aspects.TransactionLocalAspect"
  |              scope="PER_JOINPOINT">
  |    <attribute 
name="TransactionManager"><depends>jboss:TransactionManager</depends></attribute>
  |    </attribute>
  | </aspect>
  | 

The actual aspect instance is created per joinpoint/per instance.  But the 
configuration dependency still remains.

If there was something like a dynamic bean where dependencies were injected as 
defined in XML, but it had a dynmamic, generic interface, something like this 
woudl be much easier to implement.

Bill

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

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


-------------------------------------------------------
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