The current Proxy/ProxyFactory implementation tightly couples the Proxy generation code with a series of static utilities also used in validation of a deployment ie: * Same interface cannot be both business local and business remote (EJBTHREE-1025) * RemoteHome must have "create" methods of return type assignable to javax.ejb.EJBObject ...etc. I won't be including logic of this type within the "proxy" component, so I'll instead propose: * Create a new component "validation" * This component will contain a series of aspects, each tailored to one validation use case referencing back either to spec or JIRA * Interception to occur at (Session|MDB|Service)Container.start() Over time we may additionally move other validation checks out of Container code (EJB3 Core) and into the new component, but for now all I need is a good place to put the stuff coupled with Proxy generation. S, ALR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4150031#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...