[jboss-dev-forums] [Design of JBoss Remoting, Unified Invokers] - Re: Moving core o.j.invocation classes to common

[scott.stark@jboss.org]

No, the mc should not be dealing with these legacy classes:
Invocation
InvocationContext
InvocationKey
InvocationType
Invoker
JBossLazyUnmarshallingException
PayloadKey
SecurityActions 

These would need to be a legacy unified invoker artifact in a remoting subproject.

The new aop based invoker model is what needs to exist in the mc project as the basis for a unified proxy/aspect model.


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

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