hi carlos, there is a bv-api we should use. i suggested it in the eg because i saw exactly such use-cases. (myfaces extval already uses it.)
if we start such a module, we should just use the bv-api. we also need such a module for a new myfaces extval add-on (see [1]). my idea was to impl. a portable js-bv-engine. so we can use it for projects like myfaces extval as well as a gwt module. regards, gerhard [1] https://issues.apache.org/jira/browse/EXTVAL-89 http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces 2010/7/22 Carlos Vara <[email protected]> > Not really. A JSR303 validator would also need to hunt for annotations in >> a given class, as well as using reflection-based tricks to generate proxies >> for XML-declared validation constraints. All in all it would seem that a >> unified interface with various implementations would be the appropriate >> mechanism to get interoperability between GWT and libraries that typically >> use reflection in Java runtime environments. >> > > True. The good news is that the "validation" part only uses the reflection > API when it has to invoke getters. On the other way, the "parsing" phase > relies heavily on reflection. > > Doing the parsing only on the server (on init, as this is a do once step), > and having a way of transferring the validation metadata to the client > (javascript) to perform the validation there would look like the easiest > approach to me. Infact, I think bval-core has functionality for the metadata > transfer, but Roman may correct me on this. > > Regards, > Carlos > > > >> > I will down load and start poking around in the code. >> > >> > >> > My second question is, Is there interest a bval-gwt subproject? >> > >> >> I didn't want to speak for the community, but given Donald's input, I >> would agree: the more the merrier. >> >> -Matt >> >> > R, >> > nick >> >> >
