ClassCastException when trying to cast naming reference to s

[bmhardy]

Hello. I'm trying to access an session bean written with ejb3.0 from an applet. Can any one tell me why I get a ClassCastException when trying to cast the naming reference to my session bean?

Here's the exception thrown:

java.lang.ClassCastException: javax.naming.Reference
at sample.applet.AsyncEngine.init(AsyncEngine.java:43)
at sun.applet.AppletPanel.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)

Here is the code I'm using to get a handle to the session bean:

jndiProps.setProperty("java.naming.factory.initial", "org.jnp.interfaces.NamingContextFactory");
jndiProps.setProperty("java.naming.provider.url", myServer);
jndiProps.setProperty("java.naming.factory.url.pkgs", "org.jboss.naming:org.jnp.interfaces");
InitialContext ctx = new InitialContext(jndiProps);
autoMgr = (AutomobileMgr)ctx.lookup(AutomobileMgr.class.getName());

Any idea on how to fix this problem?
Thank you very much.

Brian

[donniedarko]

Check out:

"Connecting to EJB3 from within an Applet"

in the Wiki


http://wiki.jboss.org/wiki/Wiki.jsp?page=EJB3

Best regards

[lhoriman]

"bmhardy" wrote:
autoMgr = (AutomobileMgr)ctx.lookup(AutomobileMgr.class.getName());

Is AutomobileMgr a @Remote interface or a @Local one? Are you sure you don't want:

autoMgr = (AutomobileMgr)ctx.lookup(AutomobileMgrRemote.class.getName());

That error msg (about Reference) is what happens when you lookup a local interface from a remote client.

Jeff Schnitzer
http://www.similarity.net

[bmhardy]

That was a good idea.

I'm pretty sure the Mgr is Remote. I see @Remote specified in my Mgr interface, but once the code is compiled and deployed, I'm not certian where to look to verify for certain that the Mgr is Remote (even though not named with MgrRemote).

Brian

[bmhardy]

I read this off theserverside at address
http://www.theserverside.com/discussions/thread.tss?thread_id=34856

It seems there is a bug with JBoss 4.0.2. I deployed the same example ear file to version 4.0 and 4.0.2 but version 4.0.2 failed. When I lookuped the home of a bean deployed from a web servlet using InitialContext JBoss Server 4.0.2 always appended additional "Home" to the end of bound JNDI subcontext, which caused ClassCastException. The funny thing is, if you use stand-alone client there are no such exception at all.

I'm using jboss-4.0.1sp1 and see this problem

Is this comment correct?

Brian