On 23 sep, 09:56, kilaka <[email protected]> wrote:
> Hi all,
>
> GWT enables. among other things, the use of the same classes in client
> and server code.
> Client code is compiled to JavaScript and server code to Java byte-
> code.
>
> My problem is:
> If a GWT application is developed in one eclipse project - both client
> and server,
> client code can directly invoke server code and vice versa.
> The recommendation to help from making such a mistake is to use a
> package convention:
> - com.same.client for client code and
> - com.sample.server for server code
>
> This is not sufficient enough, for such mistake may still happen -
> especially when the eclipse adds imports automatically to the head of
> file in the imports section which is folded by default, causing you
> not to notice the package name.
>
> Also, there are classes that are shared by both the server and the
> client, like the Greetings interface(client uses and server
> implements). Where does it goes?
>
> I tried creating a working development environment with 3 projects:
> - Client
> - Server
> - Shared
>
> It was very complicated and needed a symbolic link from Shared to
> client - for the compilation to JavaScript.
You don't need a symlink, just add your /Shared/src folder to the
classpath in your *.launch config (and/or build.xml)
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/google-web-toolkit?hl=en
-~----------~----~----~----~------~----~------~--~---
