javax.naming.Reference cannot be cast to org.omg.CORBA.Object

[Marcel Koopman]

Hello, I've got a problem with my test class. I want to get a remote object but get a ClassCastException. (Using jBoss)

Anyone else ever had this problem? Any ideas?

                ....
                InitialContext context = getInitialContext();		
		Object modelRemoteRef = context.lookup("ModelBean/remote");
		ModelRemote modelRemote = (ModelRemote) PortableRemoteObject.narrow(modelRemoteRef, ModelRemote.class);

private static InitialContext getInitialContext() throws NamingException
	{
		Properties properties = new Properties();
		properties.put(Context.INITIAL_CONTEXT_FACTORY, "org.jnp.interfaces.NamingContextFactory");
		properties.put(Context.URL_PKG_PREFIXES, "org.jboss.naming:org.jnp.interfaces");
		properties.put(Context.PROVIDER_URL, "jnp://localhost:1099");
		return new InitialContext(properties);
	}

Exception in thread "main" java.lang.ClassCastException
	at com.sun.corba.se.impl.javax.rmi.PortableRemoteObject.narrow(PortableRemoteObject.java:229)
	at javax.rmi.PortableRemoteObject.narrow(PortableRemoteObject.java:137)
	at nl.capgemini.inzetmanagement.Client.main(Client.java:30)
Caused by: java.lang.ClassCastException: javax.naming.Reference cannot be cast to org.omg.CORBA.Object
	at com.sun.corba.se.impl.javax.rmi.PortableRemoteObject.narrow(PortableRemoteObject.java:212)
	... 2 more

[Christian Nicoll]

Hi Marcel,

perhaps there is something wrong with your line 3:

 Object modelRemoteRef = context.lookup("ModelBean/remote");  

The ClassCastException

Caused by: java.lang.ClassCastException: javax.naming.Reference cannot be cast to org.omg.CORBA.Object

makes me think that there is something wrong with your import-statements. Are you sure that you don't import org.omg.CORBA.Object or org.omg.CORBA.* ? You can also replace line 3 with the following line:

 java.lang.Object modelRemoteRef = context.lookup("ModelBean/remote");  

Best regards/Lieben Gruß,
Christian

[Marcel Koopman]

These are my import statements:

import javax.naming.Context;
import javax.naming.InitialContext;
import javax.naming.NamingException;
import javax.rmi.PortableRemoteObject;

I also tried your suggestion of:

java.lang.Object modelRemoteRef = context.lookup("ModelBean/remote");   

But still the same exception.

I remember this code was working before, does it have anything to do with the way I run it?

[Marcel Koopman]

Also i did a System.out.println of the ref object (System.out.println(modelRemoteRef):

Reference Class Name: Proxy for: main.java.nl.capgemini.inzetmanagement.beans.ModelRemote
Type: ProxyFactoryKey
Content: ProxyFactory/ModelBean/ModelBean/remote
Type: EJB Container Name
Content: jboss.j2ee:jar=inzetManagement.jar,name=ModelBean,service=EJB3
Type: Proxy Factory is Local
Content: false
Type: Remote Business Interface
Content: main.java.nl.capgemini.inzetmanagement.beans.ModelRemote
Type: Remoting Host URL
Content: socket://127.0.0.1:3873/

[Felipe Cintra]

i have same problem, but solved this replacing some libs in classpath on client side:

using JBoss-5.1.0:
concurrent.jar
ejb3-persistence.jar
jboss-aop.jar
jboss-common-core.jar
jboss-ejb3-common.jar
jboss-ejb3-core.jar
jboss-ejb3-proxy-clustered.jar
jboss-ejb3-proxy-impl.jar
jboss-ejb3-proxy-spi.jar
jboss-ejb3-security.jar
jboss-integration.jar
jboss-javaee.jar
jboss-logging-spi.jar
jboss-remoting-aspects.jar
jboss-remoting.jar
jboss-security-spi.jar
jbosssx.jar
jboss-transaction-aspects.jar
jnpserver.jar

this link help me

http://imasters.uol.com.br/artigo/12975/desenvolvimento/jboss_501ga_ejb3_maven2_e_cargo_juntos_e_na_pratica/

thanks Diego Pacheco, you save my tests

Using glassfish-v2.1:
appserv-admin.jar
appserv-cmp.jar
appserv-deployment-client.jar
appserv-ee.jar
appserv-ext.jar
appserv-jstl.jar
appserv-jwsacc.jar
appserv-launch.jar
appserv-rt.jar
appserv-rt_l10n.jar
appserv-se.jar
appserv-tags.jar
appserv-upgrade.jar
appserv-ws.jar
javaee.jar

all the libs are found in the container (jboss or glassfish) installation directory

[Mihai Radulescu]

Hi

Under jBoss the JNDI looks like : "application/BeanName/mode" where the application name is your ear name, the BeanName is the Class name for your beam and the mode is local or remote. By example : "myTestApp/MyBeanImpl/remote", this JNDI lookup search the MyBeanImp remote bean in the myTestApp ear.
Note : this works only for JBoss.

Regards,
Mihai

[shiv shetty]

hi below is the solution;

1: make this change in your code

InitialContext context = getInitialContext();
ModelRemote modelRemote = (ModelRemote) context.lookup("ModelBean/remote");


private static InitialContext getInitialContext() throws NamingException
{
Properties properties = new Properties();
properties.put(Context.INITIAL_CONTEXT_FACTORY, "org.jnp.interfaces.NamingContextFactory");
properties.put(Context.URL_PKG_PREFIXES, "org.jboss.naming:org.jnp.interfaces");
properties.put(Context.PROVIDER_URL, "jnp://localhost:1099");
return new InitialContext(properties);

2. Add jbossall-client.jar to your classpath from jboss/client folder.

[Foster Sa]

Felipe Cintra wrote:i have same problem, but solved this replacing some libs in classpath on client side:

using JBoss-5.1.0:
concurrent.jar
ejb3-persistence.jar
jboss-aop.jar
jboss-common-core.jar
jboss-ejb3-common.jar
jboss-ejb3-core.jar
jboss-ejb3-proxy-clustered.jar
jboss-ejb3-proxy-impl.jar
jboss-ejb3-proxy-spi.jar
jboss-ejb3-security.jar
jboss-integration.jar
jboss-javaee.jar
jboss-logging-spi.jar
jboss-remoting-aspects.jar
jboss-remoting.jar
jboss-security-spi.jar
jbosssx.jar
jboss-transaction-aspects.jar
jnpserver.jar

all the libs are found in the container (jboss or glassfish) installation directory

Thank you Felipe Cintra!
I registered just to thank you for your help.
You saved my day at work today.

[Vin Vikram]

We can use "jboss-as-client" instead.

For me it worked by adding this dependency in ejb client:

<dependency>
<groupId>org.jboss.jbossas</groupId>
<artifactId>jboss-as-client</artifactId>
<version>5.1.0.GA</version>
<type>pom</type>
</dependency>

Thanks,
Vin

[Vin Vikram]

We can use "D:\AppServer\jboss-as-distribution-6.1.0.Final\jboss-6.1.0.Final\client\jbossall-client.jar" in our ejb client to fix javax.naming.Reference issue.