Hello Michael While integrating an RPC service with Spring is rather easy (there exist numerous implementations), sepperating the GWT API from the service itself is not trivial. It is exactly this consideration which gave birth nearly two years ago to the SL [1] as a collaborative effort to formulate a precise implementation of what was a nearly ripe idea in everybody's mind (or at least the ones who cared ;-).
The SL allows you to define service interfaces and provide implementations that do not depend on the GWT API (as a matter of fact, not even the SL or any other API). You can create POJOs and export them to the Web via RPC-exporters, similar to the standard way Spring provides gateways of POJOs to other protocols. [1] http://gwt-widget.sourceforge.net/ On Mar 5, 3:42 pm, Michael Wyraz <[email protected]> wrote: > Hi, > > is it possible to separate the implementation if a service from the > RemoteServiceServlet? The reason is that I want to use a spring bean > as service which has a different superclass and this service is also > exported as SOAP webservice. Now I need to write a > RemoteServiceServlet that passes every service method call to my real > service implementation. That leads to (IMO) bad design. > > Regards, > Michael. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
