If you are using the command pattern (Action) then you can create a second ActionService. We have done so and can easily control this way which classes are included in the "Light"Service. It's really simple. If you have the interface ActionService with
Result execute(Action action); extend the ActionService interface with LightActionService containing the method LightResult execute(LightAction action) All your initial RPC calls should use a LightAction & LightResult. On the serverside you can use the same logic for both Services because LightAction is an Action. Probabely there is another proper way, but it workes well and doesn't need too much effort -- 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.