- The whole Invoker layer needs to be migrated to the more general remoting framework. The remoting
- There is an XMBean interceptor which implements the invoke(Invocation) handling in the 3.2.1 admin/devel book which should be rolled into the codebase. The problem here is that is has to deal with 2 types of Invocations and two type of Interceptors. This needs to be unified.
Adrian Brock wrote:
I'm currently working on a HA version, what changes do you have in mind?
ProxyFactory generates ClientContainer with client interceptors, invoker, target MBean and exposed interface (need a notion of client metadata as well). Invoker dispatches to MBean (ideally we should do method hashing here).
I was thinking about writing an extension to XMBean to receive invoke(Invocation) as well. This is a stop gap until we can use AOP in all invocation stacks. This will provide remote (local optimization) access to the POJO target with an interceptor stack. We allow the target to expose a different remote interface to the management interface (e.g. JNDI has Context for remote use and the current MBean interface for management).
Regards, Adrian
------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
