If the rmi package contains data structures/config's that you *need*
on the client side you can either make a DTO (much safer) or override
the desired classes using the super-source tag in your module
definition.
On Mar 12, 9:37 am, rudolf michael roud...@gmail.com wrote:
I dont think that you
Hi all,
i am playing around with gwt to get a gwt client - gwt-rpc - gwt
server - rmi - rmi server scenario working.
And i have the simple problem that it cannot resolv java.rmi (which is
in rt.jar - which is definitly included)
I am running gwt 2.0.x - on a 64bit linux machine under eclipse -
I dont think that you can use java.rmi, if i am not mistaken the only
package you can use from the java sdk is java.util
If rmi was supported then why in a hell you need RPCi would love to have
this option within my .cleint.*.java classes this way i will be able to
lookup all my EJBs using rmi
You CAN USE rmi, just that you can't use it with your client code.
gwt client - gwt-rpc - gwt server - rmi - rmi server
The above chain is definitely possible. I think you have inadvertently tried
to connect gwt client to RMI server, which is not possible. Move your RMI
related code out of your
