anonymous wrote : | I think you made need the concept of a DynamicBean in wich the Bean's attributes do not result in a call to a setter, but rather a generic setter. Is there something like this? | | Please take a look at: | | http://docs.jboss.org/aop/aspect-framework/reference/en/html/xml.html#xml-aspect2 | http://docs.jboss.org/aop/aspect-framework/reference/en/html/xml.html#xml-aspect3 |
Per instance and per joinpoint is also something JBossMX has. i.e. you create an interceptor for each attribute or operation. I didn't implement that in my prototype because I wanted to keep it simple. This is just a different configuration. The pseudo configs I have shown above don't include this since I wanted to keep it simple. My plan was to have Kernel/Container/JoinPoint awareness. This is a generalization of MBeanRegistration/ContainerPlugin that can be implemented by the target, but I anticipate it will be more often implemented by the aspects and subservices to define their scope and do some optimization at deployment time. Related is the notion of service/subservice where the microcontainer handles deployments like the JMXInvoker/interceptors, EntityContainer/LockManager, EJBContainer/ProxyFactory, JDBCStoreManager/FieldBridge, etc rather than each service having to provide its own solution. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3861180#3861180 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3861180 ------------------------------------------------------- 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
