@Remote(AnInterface.class)
If you are using something like that on your bean class, then the interface 
needs to be on your client classpath. Use the interface to cast it. 

AnInterface.class.cast(remoteObjLookup);

[email protected]
http://www.tomitribe.com

Sent from my mobile device.

----- Reply message -----
From: "Romain Manni-Bucau" <[email protected]>
To: <[email protected]>
Subject: EJB Deployment in TomEE 6
Date: Fri, Dec 30, 2016 10:01

You can cast it as the remote interface directly with ejbd

Le 30 déc. 2016 06:40, "sudhish81" <[email protected]> a
écrit :

> I did a JNDI lookup for the deployed bean's Remote object using a stand
> alone
> client program with RemoteInitialContextFactory and the returned object is
> of type java.lang.reflect.Proxy and not of type java.rmi.Remote. When
> deployed in IBM Websphere, the object being returned is of type
> java.rmi.Remote. So, is there any configuration I need to do so that the
> JNDI lookup returns the actual object itself rather than the Proxy?
>
>
>
> --
> View this message in context: http://tomee-openejb.979440.
> n4.nabble.com/EJB-Deployment-in-TomEE-6-tp4680839p4680841.html
> Sent from the TomEE Users mailing list archive at Nabble.com.
>

Reply via email to