OK, I see I mispoke, causing some confusion. The classes that are passed to the client are not in the client package, but in abc's gwt.xml I use the <source> tag to tell GWT where to find them. These classes are passing through to the client just fine when I run in Hosted Mode. The problem is when I run gwt:compile to deploy to Tomcat (running in production, for instance) I get errors due to external dependencies which are server-side only: dependencies on java.io.InputStream, and SimpleDateFormat. How can I get GWT compiler to ignore these?
On Jan 6, 2:58 pm, Open eSignForms <yoz...@gmail.com> wrote: > On Wed, Jan 6, 2010 at 1:10 PM, Rob Wood <rob.a.w...@gmail.com> wrote: > > The abc.jar does not include any client packages as far as I can > > tell. > > > Since the above post I've changed this project so that a few files > > from abc.jar now implement IsSerializable so they can be passed to the > > client. As a result, abc is now a GWT module which I import into my > > GWT app. Most of the functionality in abc.jar, however, is strictly > > server side. > > If you can "pass to the client" then it should be in the client package. > All classes referenced by code in the client classes must be available to > the client, and thus must be translated to javascript, etc. The fact that > you didn't put it in the client package is why it's complaining it can't > find the code. > > So I'd recommend putting anything with IsSerializable (or otherwise is > referenced by client code -- even if you just pass the object into a client > constructor and otherwise don't send it directly) in the client package so > it can be compiled.
-- 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-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
