[jboss-dev-forums] [Design of EJB 3.0] - Re: EJBTHREE-1454 Encapsulate Container infomation in TO/VO

[ALRubinger]

"jaikiran" wrote : 1) Is there any naming convention that is followed for VO in the project?

I wonder if we can simplify this further:

The contract between the EJB3 Core Containers and EJB3 Proxy is InvokableContext.  Because this whole process of JNDI Binding doesn't cross a network boundary, you can probably skip the whole value object thing and just pass in the Container itself.

So try adding accessors for the properties mentioned to InvokableContext, making sure they line up with the actual method names used by EJB3 Core SessionSpecContainers, and then EJB3 core can do a JndiSessionRegistrar.bindEjb(otherParams,this)...

"jaikiran" wrote : you think, we should even encapsulate the jndi context in the VO?

Yes, by the same mechanism, use whatever "getContext" or "getInitialContext" is available in EJB3 Core Containers and add this to the InvokableContext contract.

S,
ALR

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

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