This relates to the following thread: http://www.jboss.org/index.html?module=bb&op=viewtopic&t=57054
What I want to do is build containers using dependency injection and where the different facades can use the same stack. Use cases: 1) A service that has a @transaction tag waits for the transaction manager to be deployed because the transaction demaraction aspect has that dependency defined. 2) Redeployed of a service (the transaction manager in the above use case) causes the dependent services (the bean with the @transaction tag in the above example) to "redeploy". By redeploy that might just be to suspend the service on a valve while the transaction manager recycles. It will depend upon configuration/usage. 3) A service deployed with @mbean tag will automatically get a DynamicMBean facade/introduction and "registered" with the JMX MBeanServer. This will just target the requests at same interceptor stack whether it uses the DynamicMBean facade or the plain POJO front end. 4) Fundamental to a simple design (see the thread mentioned above) is that the container itself can be built through dependency injection. i.e. the container/interceptors are javabeans that be controlled through IOC. The question is how close are we with the AOP container to do this? I have already prototyped some of this with a custom container/jmx implementation in the kernel module. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3860611#3860611 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3860611 ------------------------------------------------------- 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 [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-development
