I'm guessing that the validation is mostly just "hand waving" at this point. If you have a specific use case, I would recommend adding a blip at or around that area.
On Jun 3, 4:08 am, Stefan Bachert <[email protected]> wrote: > Hi, > > Spring Roo and GWT seems not very stable, yet. > > I tried to run the clinic sample from Spring roo with an "setup gwt". > This does not work at the moment (Spring roo 1.1.0M1, due to missing > classes). > > Spring roo is an interesting thing, however, the version 1.1.0.M1 is > not really usable for GWT. > > Stefan Bacherthttp://gwtworld.de > > On 2 Jun., 16:16, jbdhl <[email protected]> wrote: > > > > > I came across the work-in-progress design document for RequestFactory > > for GWT2.1 in this > > wave:http://www.google.com/url?sa=D&q=https://wave.google.com/wave/%3Fpli%... > > > The document does not directly describe the data binding, AFAICS, but > > it seeded some related questions that I can't figure: > > > 1a) The examples in the wave show validation annotations for the > > model properties, e.g. something like > > @Length(4,10) > > I assume that the validation code generated from these > > annotations will be reusable on the server? > > > 1b) Will it be possible to implement our own validation code, > > > 1c) and will the feedback messages be i18n-able? > > > 2) The document mentions development using Roo to maintain the > > boilerplate code. But us that use objectify instead of JDO will > > probably not be able to use Roo because Roo does not currently support > > objectify. Am I correct? > > > Any hints would be much appreciated. :-) -- 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.
