Thanks for the information. You mentioned that the "GWT front-end makes requests to the DB through object streams over sockets". How are you achieving this? Does the client application also have a server component? That is, is this the interaction:
Browser ----------- GWT RPC --------> Server ------ Socket connection to DB ----> DB ? What I'm trying to get at is that if the object classes that you're sending over GWT RPC are actually defined in your DB project, then the source for those classes needs to be made available to your client project during the compilation process. In order to do this, you'll need to define a GWT module in your DB project so that you can pull in the source. Does that make sense? On Sat, May 16, 2009 at 2:29 PM, Tim McCormack <[email protected]> wrote: > > On May 15, 5:16 pm, Rajeev Dayal <[email protected]> wrote: > > So, it seems that you client project needs access to classes in your > > Java-only project (the shared classes). Why is this? Are these classes > that > > need to be used for GWT RPC? > > There are two main projects. One is a big ol' database, which is all > regular Java. The second is a GWT project that serves as a front-end > to the database. The GWT front-end makes requests to the database > through object streams over sockets, and the objects they send back > and forth need to be instances of shared classes. > > The DB core does not know about the front-end GUI stuff, and vice > versa. > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
