[jboss-dev-forums] [Design of EJB 3.0] - Re: EJBTHREE-786

[bill.burke@jboss.com]

I keep saying this to you....

I know the intention of the specification.  We can challenge any TCK test based on knowledge of this intention.  IIRC, the spec says *nothing* about requiring an EJB 3.0 reference to be castable or narrowable to EJBObject.  This is just something *JBoss* threw in.

Also, it is *impossible* to know what interface was invoked upon if a set of interfaces of the same type (remote/local) have a method of the same signature.

The implementation of this, BTW, is very easy.  Have knowledge on whether the method was invoked remotely or locally or through web services.  Save the method hash transferred through the web layer.  When somebody invokes getInvokedBusinessInterface, take this information and match the method hash to the appropriate interface.  First one wins.

Why are we overengineering for this case?

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

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