ClassCastException when updating ear-jar.xml schema to be EJ

[logankiefer]

I'm using JBoss 4.0.4GA with EJB RC7. My current ejbs are all 2.0 ejbs and I want to keep using the deployment descriptors. I'm updating the ear-jar.xml schema to use ear-jar_3_0.xsd instead of the ear-jar_2_0.xsd.

When I change the ejb-jar.xml to use ejb-jar_3.0.xsd the context.lookup(jndiName) is returning a proxy that does not extend the EJBHome interface. If I change back to the ejb-jar_2.0.dtd the Proxy does extend javax.ejb.EJBHome.

Does this mean in order for my EJB 2.0 beans to be EJB 3.0 compliant (i.e. use ejb-jar_3.0.xsd) I must now remove all occurances of casting the Proxy object, returned from a context.lookup, to EJBHome???

[logankiefer]

Some more testing shows that the exact same lookup will return an object that implements a Home interface when using ejb-jar_2_0.xsd and it will return a an object that implements the Remote interface when using the ejb-jar_3_0.xsd

Lookup Code below:

EJBHome home = (EJBHome)PortableRemoteObject.narrow
(context.lookup(sJNDIName),narrowTo);

The same sJNDIName is used in both cases. The only thing that changes is the xsd.

[bill.burke]

home interfaces are registered in JNDI under:

BeanClassName/remoteHome

BeanClassName/localHome

[logankiefer]

Does this mean instead of passing in a JNDI name of ejb/LoginController to the context lookup I should use LoginControllerBean/remoteHome?

LoginController EJB names for reference in this example:

Home Interface = LoginControllerHome
Remote Interface = LoginController
Bean = LoginControllerBean.

[logankiefer]

I read in the Enterprise EJB 3 book that the default JNDI binding ofr a remote interface is obtained by concatenating the ejb name with /remote So, for my example above it would be 'LoginControllerBean/remote'. However, I recieve the same ClassCastException.

I'm not sure what other information I could provide that would help gleam some light on this problem.