GWT creates 2 packages for you: client and server. For the subject of shared code, and especially DTO's, this is kind of weak; architecturally. You don't want to include "client" code on the server - it just ... smells wrong.
I create a third package, given com.myco.client, and com.myco.server, I create com.myco.shared. in your Module.xml, just add the 2 lines: <source path="client"/> <source path="shared"/> ESPECIALLY if you are building a "library", make sure your build includes both the .class and .java under shared in your jar. I also put my RemoteService interfaces there. For DTO's, I create com.myco.shared.transport. I find this method helps everyone on the team understand the role of the classes in the package. ALSO, I ALWAYS name my RPC servlet bindings ending with .rpc. In the web.xml I can more easily add filters and security, or know what is being called watching in Firebug, etc. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
