ClassCastException upon jndi lookup after upgrade from 3.2.8

[hgsdc]

Hi forum.

I have already searched the forums and wiki and found that this might be class loader related. I just can seem to get it working. Here's the scene:

I have a web app placed in a war file, say app-web.war
I have a ejb app placed in a ejb jar file, say app-ejb.jar
The whole thing is packed in an ear file, say app.ear

All interfaces are local.

I get the classcast exception during casting of the found home interface (via jndi) to the concrete home interface:

In my web app servlet I do:

MyHome home = (MyHome) ServiceLocator.GetHome(serviceId)

In the ServiceLocator static class i perform the lookup in jndi:

// Lookup is just fine
Object ref = initial.lookup(getServiceName(serviceId));

// Cast to the common EJBHome interface
return (EJBLocalHome) ref;

Upon casting to MyHome interface in servlet I get the class cast exception.

Can someone instruct me how to exactly pack my app-web.war, app-ejb.jar and the app.ear to overcome this issue?

I built my ear and it's contents with an ANT script.

Thanks in advance.

Regards

Henrik

[jaikiran]

Have a look at http://wiki.jboss.org/wiki/Wiki.jsp?page=ClassCastExceptions especially the jmx-console method mentioned over there.

[hgsdc]

Hi jaikiran

Thanks for the link. Exactly that link did not catch my attention as I was searching the wiki :-(

But as I am diving into this issue I guess I know what to do to resolve. Repackage the ear. I have already done so and it is bringing me further.

With respect of this beeing the JNDI forum:
I have classes that really are shared among the two jars: app-web.war and app-ejb.jar. Would it be approriate to let those classes to into one single jar, say app-shared.jar, that is then put into the ear? This would give them a "unique identity" with respect of the class loader right?

Thanks in advance. You helped me alot already.

Regards

Henrik

[jaikiran]

If the class is meant to be used by both the war and the ejb-jar, the way i package it is - i create a separate jar (common-util.jar maybe) and make it available to both the war and ejb modules by specifying the common-util.jar as java module in the application.xml file of the ear. You can find more details about the same at:

http://jaitechwriteups.blogspot.com/2006/10/how-to-package-application-into-ear.html

The common-util.jar will be loaded by a single classloader and will be made available to both the war and the ejb-jar.

[hgsdc]

Hi jaikiran

Yup, exactly what I would suspect to happen. Thanks for link. It was exactly what I was trying to do. No more classloading problems whatsoever. Simple put: GREAT. Thanx

Best wishes and regards

Henrik