And I don`t have a lot experience with validating frameworks. With our current platform validation is not as strong as it could be. But I hate the fact that validation is drawn from the domain object into the gui. I think validation should be done in the domain object (or with the logic in a seperate validator.. just like the seperation of the dao) but in essence it should belong to eachother and not be scattered in different files (xml.. aarrgghh..) and a lot of different places. So.. maybe make a lot of the validation part of the domain object where it belongs..
________________________________ From: [EMAIL PROTECTED] on behalf of Eelco Hillenius Sent: Mon 18-7-2005 21:12 To: [email protected] Subject: Re: [Wicket-user] why such a strange design in the AbstractValidator I agree that's an improvement. It's less elegant that we have all those methods carrying the instance of FormComponent now, but it is better to have validators thread safe by default. If we're going to change this, it will mean an API break for a lot of clients, so this will be 1.1 only. And while we're at it, let's see if we can improve the validation part further. Phil just filed this: https://sourceforge.net/tracker/?func=detail&atid=684978&aid=1240458&group_id=119783 with which I also agree. Do other people have votes/ idea's on this? Eelco ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
<<winmail.dat>>
