"jaikiran" wrote : + /** | | + * Returns the initial context | | + * @return | | + */ | | + InitialContext getInitialContext(); Let's make that just return Context, otherwise, yup. "jaikiran" wrote : 1) The interface InvokableContext sounds generic and probably can be used to carry out any generic invocation. So is it appropriate to introduce getGuid (and similar) method here? What i mean is, do all invocable objects need to have a Guid? Keep in mind that everything here is implicitly pertaining to EJB3 Proxies, so I think all of the methods above are necessary for a contract between the EJB3 Container and the Proxy component (InvokableContext sounding more generic aside). So long as we're making sure that Proxy *needs* all this information, and we're not bleeding EJB3 Core internals outside, we're OK. "jaikiran" wrote : 2) The following 2 methods are not available in the EJB3 Core SessionSpecContainers. ... | | String getName(); // Currently the EJB3 core, generates a name based on getObjectName().getCanonicalName() getName() is inherited by way of EJBContainer... "jaikiran" wrote : String getGuid(); // EJB3 Core, currently uses Ejb3Registry.guid(this) to generate this True story. Even though the true state is held in Ejb3Registry, I suppose this could be considered an extended property of the container, so go ahead and expose a getGuid() there which delegates back to Ejb3Registry. "jaikiran" wrote : 3) I see that the getAdvisor method is deprecated on the EJBContainer: | | | @Deprecated | | public Advisor getAdvisor() | | { | | return beanContainer._getAdvisor(); | | }Any specific reason? Yes, because the EJB Containers have been refactored a few too many times and we'd really like to tuck away the underlying Advisor, but really can't just now because too many outside components depend upon its exposure. S, ALR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4171681#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...