Pakin, Comments in-line... .
Pakin wrote: > That's OK, > > although I want to clarify that they are related matters as what I was > suggesting has to be also reflected in client validation. Okay... you mentioned JSR-303 but didn't mention client side validation so that was the disconnect. > Pretty much the use case would be the following: The framework detects if > there is any JSR-303 provider in the classpath, if so it uses all your JPA > annotated pojos that are binded to any form, I am right there with you. And this is where Stripes validation doesn't go far enough. > so the stripes taglibs would > generate client validations at jsp rendering time. Though Stripes validation does attempt to help in this regard with the field-metadata that can be injected into a form > Somehow this client > validation should be able to be cross-javascript-framework sort to speak. > Stipes-stuff has jQuery files that integrate Stripes field-metadata. > Although I reckon that jQuery is the de facto standard here. Why do people feel inclined or the need to call JQuery a de facto standard. It's a framework that is popular. There are many other JS frameworks that are as good and for the OO purists perhaps even better. It's like saying Spring MVC is the de facto standard of web frameworks. In any event, my personal take is that MooTools is like Stripes... maybe not the most popular... but the best thought out. > Once the form > is submitted the system detects if the form backing bean is a persisted > object with JPA annotation and perform the validations among other > validations you may have. This way you don't need to repeat your DB backend > related constraints using the custom Stripes validation annotations. IMHO it > would be a very agile and convenient feature. > It would be very convenient and barring the JSR-303 aspect Stripes does that today... at least w/ the help of Aaron's Stripes Stuff. I was hoping that someone had done something similar w/ MooTools. And I agree that JSR-303 is the way to go and that the entire validation process from server, through client, through annotations (JPA, what not,...) needs to be thought out and built into Stripes in a proper and robust manner. So are you volunteering... like I said there was a post on this mailing list w/ some JSR-303 code... ;-) Cheers, --Nikolaos > Cheers mate, > > Angel. > > > Nikolaos Giannopoulos wrote: > >> Pakin, >> >> Welcome to this mailing list. It's great that you are interested in >> collaborating. >> I totally agree that Stripes needs work in the Validation area on the >> server side... and any thoughts would be welcome. >> >> However, this specific thread is about how to hook in "client" side >> validation so as to pre-validate form input so as to improve the user >> experience, reduce server load, etc... . I don't believe JSR-303 has >> anything to offer here? Does it? >> >> ASIDE: Feel free to start a new thread on JSR-303 Validation. In fact, >> if you look in the archives someone provided some code (although I don't >> recall the details, how thorough it was, etc...). Again, I don't get me >> wrong but I think another thread might be very worthwhile... . >> >> --Nikolaos >> >> >> >> Pakin wrote: >> >>> Hi all, >>> >>> I am new in town and I would like to collaborate... >>> >>> I think that validation-wise, it would be more interesting trying to >>> tackle >>> the issue of: how to integrate Stripes server and client validation with >>> JSR-303 >>> >>> Frameworks like Spring MVC 3 or Loom already have it and I think it is >>> indeed a competitive advantage over Stripes. >>> >>> I think Stripes validation should adopt JSR-303 because it is standard >>> and >>> most of the constraints to be validated come from the database and >>> currently >>> with stripes you have take care about those explicitly. >>> >>> You can find more information about what Spring MVC does here: >>> http://static.springsource.org/spring/docs/3.0.0.RC3/spring-framework-reference/html/ch05s07.html >>> http://static.springsource.org/spring/docs/3.0.0.RC3/spring-framework-reference/html/ch05s07.html >>> >>> >>> Cheers, >>> >>> Angel. >>> >>> >>> Nikolaos Giannopoulos wrote: >>> >>> >>>> Hi, >>>> >>>> I noticed the following page which shows how to integrate Stripes w/ >>>> client side validation via JQuery: >>>> http://www.stripesframework.org/display/stripes/Validation+Reference#ValidationReference-Usingthe{{fieldmetadata}}tag >>>> >>>> Has anyone done anything similar w/ MooTools? >>>> >>>> If so, was it a rewrite of Aaron's code or did it hook into MooTools >>>> Form Validation? >>>> >>>> And if so - anything shared would be appreciated. >>>> >>>> We are debating whether to do this now (though are short on time - what >>>> else is new) but anything that accelerates that could help us and in >>>> turn we would post it back to the community. I also realize the effort >>>> isn't huge but JQuery notation is new to me and doing this right w/ >>>> MooTools and classes will result in a pretty extensive re-write I'm >>>> afraid. >>>> >>>> Lastly, this is probably a stretch but did anyone solve the localization >>>> issue in all of this i.e. localized error messages exist in resource >>>> bundles on the Stripes server side yet the messages need to be >>>> accessible to provide the correct message to the user... Ajax is one >>>> possibility... using a generic set of translated messages is another... >>>> but all don't appear optimal. >>>> >>>> Much Appreciated. >>>> >>>> --Nikolaos >>>> >>>> ------------------------------------------------------------------------------ >>>> Centralized Desktop Delivery: Dell and VMware Reference Architecture >>>> Simplifying enterprise desktop deployment and management using >>>> Dell EqualLogic storage and VMware View: A highly scalable, end-to-end >>>> client virtualization framework. Read more! >>>> http://p.sf.net/sfu/dell-eql-dev2dev >>>> _______________________________________________ >>>> Stripes-users mailing list >>>> [email protected] >>>> https://lists.sourceforge.net/lists/listinfo/stripes-users >>>> >>>> >>>> >>>> ------------------------------------------------------------------------------ Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today http://p.sf.net/sfu/msIE9-sfdev2dev _______________________________________________ Stripes-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/stripes-users
