And what if i want to use a package both on the client and server
side, but one of the classes has imports from app engine witch cannot
be used in GWT. Can i instruct the compiler (let's say in the .gwt.xml
file) to exclude a class from a package when compiling ?
On Jul 29, 6:18 pm, Nuno
On 24 août, 12:28, Ice13ill andrei.fifi...@gmail.com wrote:
And what if i want to use a package both on the client and server
side, but one of the classes has imports from app engine witch cannot
be used in GWT. Can i instruct the compiler (let's say in the .gwt.xml
file) to exclude a class
this is the correct response, tho, I put all inter-client-server
classes in shared/rpc, or some such package.
On Jul 29, 11:10 am, Paul Robinson ukcue...@gmail.com wrote:
You want this in your gwt.xml file:
source path=client/
source path=shared/
Note that if any source... element
Hello,
I'm trying to use a class (let's say Contact) on both client and
server sides (packages: com.app.client and com.app.server). For that
purpose I created a shared package (com.app.shared) in which to put
the Contact class. But gwt (client side) only sees classes in
com.app.client package.
You want this in your gwt.xml file:
source path=client/
source path=shared/
Note that if any source... element appears in your gwt.xml, then the
implied client source path is not added for you - so you will need both
of the above.
Paul
Ice13ill wrote:
Hello,
I'm trying to use a class
That worked... thanks a lot :)
On Jul 29, 6:10 pm, Paul Robinson ukcue...@gmail.com wrote:
You want this in your gwt.xml file:
source path=client/
source path=shared/
Note that if any source... element appears in your gwt.xml, then the
implied client source path is not added for
Also, if you class is just a pojo you dont really need to create it in two
places...
the server code can access all of your client code.
You just need to make the classes you want to transport from client to
server or vice versa.
In your example Contact may stay in the client package, and if you
