i'm unfamiliar with SOP and gwt policy files, i havn't tried much of rpc aside form the fact that each service should only object of input and object of output both extending RequesInput and RequestOutput interfaces (generic wise) to avoid break method signature incase of changes .
i then moved on to request factory and editor framework, this is where i'm having problems getting a grasp to it. btw maybe you should check out my feature request for gwt's plugin handling of gwt.xml module files. On Tue, Jun 21, 2011 at 3:51 PM, Ramon Salla <[email protected]> wrote: > Yes. We are already doing this. > We started using RequestBuilder and Json (Des)Serialization but we ended up > using plain RPC services as development is so much easier. We are wrapping > some of those RPC services with REST using jersey. > We have two dependent projects one with server code and the other with > shared and client code. > Be careful with this because of SOP and GWT policyFiles! they are tricky. > > Ramon Salla > > -- > You received this message because you are subscribed to the Google Groups > "Google Web Toolkit" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/google-web-toolkit/-/GYcElCLyMDgJ. > 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. > -- 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.
