The import java.rmi cannot be resolved

1,450 views
Skip to first unread message

Wolfgang Pichler

unread,
Mar 12, 2010, 4:22:47 AM3/12/10
to Google Web Toolkit
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 - App
engine deactivated.

Could it be that this problem is related to the 64 bit linux machine -
gwt support for 64 bit ?

best regards,
Wolfgang

rudolf michael

unread,
Mar 12, 2010, 9:37:37 AM3/12/10
to google-we...@googlegroups.com
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 RPC....i would love to have this option within my .cleint.*.java classes this way i will be able to lookup all my EJBs using rmi :(

regards,
Rudolf Michael


--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To post to this group, send email to google-we...@googlegroups.com.
To unsubscribe from this group, send email to google-web-tool...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.


Sripathi Krishnan

unread,
Mar 13, 2010, 2:06:40 AM3/13/10
to google-we...@googlegroups.com
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 xxx.yyy.client package and things should run fine.

If it still doesn't work, you would need to provide some stack traces or logs.

--Sri
http://blog.530geeks.com

dolc...@gmail.com

unread,
Mar 12, 2010, 12:15:10 PM3/12/10
to Google Web Toolkit
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 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 RPC....i would love to have
> this option within my .cleint.*.java classes this way i will be able to
> lookup all my EJBs using rmi :(
>
> regards,
> Rudolf Michael
>

> On Fri, Mar 12, 2010 at 11:22 AM, Wolfgang Pichler <wpich...@callino.at>wrote:
>
>
>
> > 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 - App
> > engine deactivated.
>
> > Could it be that this problem is related to the 64 bit linux machine -
> > gwt support for 64 bit ?
>
> > best regards,
> > Wolfgang
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Google Web Toolkit" group.
> > To post to this group, send email to google-we...@googlegroups.com.
> > To unsubscribe from this group, send email to

> > google-web-tool...@googlegroups.com<google-web-toolkit%2Bunsubs cr...@googlegroups.com>

Reply all
Reply to author
Forward
0 new messages