Sorry, I'm a c# transplant. I want a create a class that will be used
on server side only. In c# I would just create a new class in the
project... learning that java doesn't work that way. I have created a
class within the main package of my GWT project (not client, not
server, not shared, the
Nothing should be preventing you from creating non-client classes
anywhere in the hierarchy, AFAIK. The gwt.xml file is just some meta-
data used by the GWT compiler to build the client-side js code;
includes of other modules, pointers to the client code etc. There
should be no restrictions on
Actually, its nothing to do with the Java language explicitly. GWT is
cleverly organized to make it quick and comparatively easy to build
sophisticated Ajax apps without having to get too much into the details
of Javascript.
In a GWT project the GWT compiler cross-compiles a subset of the Java
Well I'm also doing it on App Engine if that adds a 4th learning
curve ;) Java code looks pretty much like C# so I think I can easily
learn that part of it.
I moved the code to the server package. When I start the server I get
this message:
Loading modules
com.mycomp.foo.bar.bar
Ok, this is just a simple GWT setup issue. When you start GWT, the
main argument is the module you're running, in your case
com.mycomp.foo.bar.bar. This isn't a java class, but an xml file that
has the metadata to tell GWT about your client app, and potentially
any servlet you want run,
