"gavin.king(a)jboss.com" wrote : "bill.burke(a)jboss.com" wrote : 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. | | Correct, the spec does not require this. In fact, it says the exact opposite in section 3.4. | Exactly and because we threw this in we get the remove signature problem. How about we take out the explicit binding of EJBObject in the proxy factories. If one of the interfaces extends EJBObject it'll be picked up again. The home interface will be bound to .../home anyway (or bound together if requested), which is always a EJB 2.1 home interface, so no clash there. Only the EJB 2.1 home should return proxies which implement EJBObject. So .../remote and .../local should all be EJB 3 bindings. Which leaves getInvokedBusinessInterface. I really would like to see it return the invoked business interface. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4090770#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...