EJB lookup problem using local client view at "java:global/.." (from outside EAR)

[rakcheru]

Jboss : 7.1.1

EJB 2.1

Hi,

My deployment scenario consists of an EAR and a separate WAR as follows

- An Ear

    |_ EJB jar

    |_ EJB Client Jar

- Another War

    (contains EJB Client Jar in WEB-INF/lib folder)

When the EAR is deployed, i can see that the EJB (with both remote and local client views) is deployed at following "java:global/.." JNDI locations apart from other locations

		java:global/Ear/Ejb/LocalAndRemoteBean!package.LocalHome
		java:global/Ear/Ejb/LocalAndRemoteBean!package.Local

An EJB client servlet (in "Another WAR") is not working when it tries to use local client view at "java:global/.." locations. The lookup using following JNDI names is returning an object. However, any casting attempt using either LocalHome or Local interface is resulting in ClassCastException.

		java:globa/Ear/Ejb/LocalAndRemoteBean!package.LocalHome
		java:global/Ear/Ejb/LocalAndRemoteBean!package.Local

The lookup code in both cases are as follows

LocalHome localHome = (LocalHome)ctx.lookup("java:global/Ear/Ejb/LocalAndRemoteBean!package.LocalHome");
Local l = localHome.create();
l.businessMethod();

Local local = (Local)ctx.lookup("java:global/Ear/Ejb/LocalAndRemoteBean!package.Local");
local.businessMethod();

The lookup returned objects of following types respectively

package.LocalHome$$$view3

package.Local$$$view4

My question is : "If the lookup is returning an object, what should be done to invoke the business method ?"

Thanks in advance

[pmm]

Here's the set up I would use: move the WAR into the EAR

- An Ear

    |_ EJB jar (content of EJB Client Jar missing)

    |_ lib/EJB Client Jar

    |_ Another War (EJB Client Jar not in WEB-INF/lib)

Then you can use use @EJB or the JNDI names that JBoss AS logs during start up

[wdfink]

@EJB is not available with EJB2, it might work under some circumstances but can have issues.

[wdfink]

Packing several ejb-client jars in your application can be problematic and have classloading issues - as you see.

You should have only the EAR/lib/ejb-client.jar and the classes not somewhere else.

Also you can use the lookup with "app/Ejb/..." approach to prevent from using the ear name.

[pmm]

Wolf-Dieter Fink wrote:

@EJB is not available with EJB2, it might work under some circumstances but can have issues.

I didn't see that, JNDI look in this case. Geez people are still using EJB2?