Just a couple of other comments on this general topic. 1. Yes, it's one-class-per RPC method. This is actually a good thing, since it lets you do item 2, which is: 2. You can add 'undo' to your actions. This is particularly handy if you build your Action classes using item 3: 3. You can have one action which executes multiple other items. This means you're using the command pattern on the server side too, not just from the client side.
When you add them all together, most of your actual functionality is encapsulated in command/action classes. I use the same service implementation on the server side as the client side, so there is really just one shared service now (I call it 'Dispatch') rather than having various services for different application functions. But for me, the biggest win is 'undo' - it's essentially like having transactions for Java code, not just database code. Not quite as bullet-proof, since some actions can't actually be undone, but a big step in that direction. I will see if I can get the code abstracted enough from my app to post it publicly. David --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
