How best can I deal with my gwt.rpc files in noserver mode in case I have multiple gwt modules that all talk against the same backend? What I do now: include the generated gwt.rpc files in my backend such that gwt can find them (I use gwt-sl spring integration).
However, I find it a bit akward and doesn't feel right... Isn't there a more easy way to merge the generated files in one gwt.rpc file (it contains duplicatted objects) ? Should I simple crap the generated gwt.rpc files and put them in my war during the maven war build?.. or can it be smarter. How do other people do this? I noticed gwt is having this new DeRpc system, but I think it doesn't solve the above issues. However, it will become more easier to run hosted mode against an other server :).. Please some advice on the above, Ed -- 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.
