Hi Daniel.
That makes sense when internally you create Jars for modules to use in
multiple projects.
We are not using doing that. We inherit sub-modules in different ("top-
level") modules that we GWT compile.
So the Javac/GWT compile takes care of all that.... putting the .class
files into /war/WEB-INF and the JavaScript files into /war/module
name.
The problem is the third-party GWT library jars we are using. I'm
looking at them now, and many of them (gwt-maps, gwt-visualizations,
etc) will be client side only, others may have server code in them
(need to be very generic server side code to be included in a GWT
library jar)....
So, I guess I'll have to split into three types of jars
- server side only jar -> normal case, nothing to do with
GWT. Just copy to /war and deploy
- GWT client side only -> I could not include these in /war at
all....
- GWT server+client code -> Need to split them up somehow (if any
exist)
--
You received this message because you are subscribed to the Google Groups
"Google App Engine for Java" 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-appengine-java?hl=en.
