|
From: Matt R. <li...@ra...> - 2004-05-26 02:57:11
|
See comments below. On May 22, 2004, at 12:13 PM, j=FCrgen h=F6ller [werk3AT] wrote: > Matt, > > We still haven't decided on how to proceed with the Commons Validator=20= > stuff; for the time being, it remains in the sandbox. If you like,=20 > please create an issue in our JIRA for it! I can certainly create an issue in JIRA if that's what's needed to get=20= it moved into the core. > > As far as I see, it's just 8 classes, including a specific JSP custom=20= > tag; so I could imagine that we include it as part of the Spring=20 > distribution. I'm not sure if it should be part of Keith's emerging=20 > "spring-rules" subproject; that's rather gonna be a separate=20 > rules-based validation engine with its own plug into Spring's=20 > validation. And 8 integration classes aren't a convincing candidate=20 > for an own subproject either. > > You have used those Commons Validator integration classes pretty=20 > intensely, haven't you? Do you already consider them comprehensive=20 > enough for a release? Do you see any room for improvement there? Do=20 > you know of any existing alternative validation libraries that people=20= > could also want to have plugged into Spring? (To me, Commons Validator=20= > seems to be the only candidate for direct support in Spring at this=20 > point of time.) To be honest, Commons Validator is the only validation engine I've=20 worked with, but I've got a few years of experience with it. It's=20 suited my needs well for those years and I especially like it's slick=20 integration with XDoclet. I do consider them stable enough for a=20 release - though I can't back it up with any real-world experience. My=20= current real-world projects use Struts for the MVC layer and Spring=20 beyond that. One enhancement I'd like to see to commons validator (or=20= another declarative validation engine that allows client-side=20 validation) is the ability to define expression rules. WebWork has=20 this with its OGNL expression support. Don Brown also has a nice=20 example of using XPath expressions with commons validation - at=20 http://tinyurl.com/33ekr. > > I wouldn't mind Spring 1.0.3 as target milestone for it, provided that=20= > we agree that Commons Validator support should be part of the Spring=20= > distribution. Interestingly enough, we already ship=20 > commons-validator.jar, because it is a runtime requirement of Struts -=20= > so we wouldn't even have to ship any further dependencies. Nice. Matt > > Juergen > > > ________________________________ > > Von: spr...@li... im Auftrag=20= > von Matt Raible > Gesendet: Sa 22.05.2004 17:27 > An: spr...@li... > Betreff: Re: [Springframework-developer] Preparing for 1.0.2 > > > > It doesn't appear that the Commons Validator stuff will be in this > release. Will that be in a future release - or is it dependent on the > declarative validation framework (that I believe Keith is still = working > on)? > > Matt > > On May 22, 2004, at 8:10 AM, j=FCrgen h=F6ller [werk3AT] wrote: > >> Hi everybody, >> >> I've just finished my final preparations for our upcoming Spring >> release 1.0.2, scheduled for Sunday night. See the changelog for >> details; most issues have been discussed on the mailing lists or in >> JIRA. All remaining issues in JIRA have been addressed but do not >> incur Spring changes; I plan to close most of them at the time of the >> 1.0.2 release, resolved as "Won't fix". >> >> I've also updated our dependencies: FreeMarker 2.3 RC4, Hibernate >> 2.1.3, iBATIS SQL Maps 2.0 RC4, Velocity Tools 1.1 final, Commons >> Attributes May 9th snapshot. (Will Commons Attributes ever get out of >> the Jakarta sandbox?? At least some sort of official beta release >> would be nice.) BTW, MockObjects is no longer in our libraries, >> neither in CVS nor in the release distribution, as we don't use it >> anymore. >> >> I plan to create the actual release Sunday night. So for all you >> weekend workhorses out there, there's still a chance to test and >> review the current CVS head :-) Please no further enhancements, >> though: As the changelog shows, we've already gathered a lot of minor >> bugfixes and enhancements, so we should get out 1.0.2 ASAP. Further >> enhancements should go into 1.0.3, scheduled for late June. >> >> Juergen >> >> >> >> ------------------------------------------------------- >> This SF.Net email is sponsored by: Oracle 10g >> Get certified on the hottest thing ever to hit the market... Oracle >> 10g. >> Take an Oracle 10g class now, and we'll give you the exam FREE. >> http://ads.osdn.com/?ad_id149&alloc_id(tm)66&op=CCk >> _______________________________________________ >> Springframework-developer mailing list >> Spr...@li... >> = https://lists.sourceforge.net/lists/listinfo/springframework-developer > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: Oracle 10g > Get certified on the hottest thing ever to hit the market... Oracle=20 > 10g. > Take an Oracle 10g class now, and we'll give you the exam FREE. > http://ads.osdn.com/?ad_id149&alloc_id=9966&op=3Dick > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: Oracle 10g > Get certified on the hottest thing ever to hit the market... Oracle=20 > 10g. > Take an Oracle 10g class now, and we'll give you the exam FREE. > http://ads.osdn.com/?ad_id149&alloc_id=9966&op=CCk > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer |