Good idea.
Eelco
Igor Vaynberg wrote:
3. One of the things I wanted to tackle with this issue was that code
like updating form components in a validate method doesn't make much
sense. The whole processing should be broken up in clearer steps with
methods that fit them, I'd like to see whether IFormValidationStrategy
still suffices and we may need to provide a couple of call back/
template methods so that users can 'intercept' in the form processing.
I'm still thinking about the best way, but jet lag strikes again.
How about renaming IFormValidationStrategy into IFormProcessingStrategy and
having validation as part of that. That will clean things up since
validation is part of processing.
Igor
-------------------------------------------------------
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-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop
-------------------------------------------------------
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-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop
