To simple reuse the services classes and the vo classes I would separate them in a diferent module... export them...(with the .java) and reuse on another module... the main point in my opinion would be to configurate the service url...
On Apr 28, 3:30 pm, JoeB <[email protected]> wrote: > I get the general idea, but I'm a little unclear on implementing the > non-GWT interface in parallel to GWT-RPC. The beauty of GWT-RPC is > that the ValueObjects I create in my client package are automatically > serialized/deserialized by GWT, and my client code and server code are > developed with the same Java class. If I want to make the same > ValueObjects accessible via a different interface (e.g. REST, SOAP, > etc), then that means I'll have to transform them into some protocol > on the wire (e.g. convert to XML or JSON). The tricky part is that > the ValueObject classes are defined in the GWT client package, but > they need to be modified in some way to perform this server-side > transformation for a different interface, and that transformation code > shouldn't leak into the GWT client. I guess what I'm saying is that > it seems like a problem that the ValueObjects are defined in the > client package because they need to be used for a non-GWT interface in > the server. Know what I mean? > > -- Joe --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
