+1 for having the validations action-based! Since maybe a class handles different actions (read methods) it will need to have different set of validation rules for each action.

Armond


Fred Lamuette wrote:


It seems that the validation framework applies only to the action
properties.
In this case, using the ModelDriven interface for action and
ModelDrivenInterceptor prevent from using the validation framework
correctly, because we need reference the properties as follows :
- "model.name" in the MyAction-validation.xml because of properties derives
from Action and not the stack
- "name" in the forms fields (due to ModelDrivenInterceptor)
So a name mismatch appears when retrieving the errors from the views
(especially in the errors processing in controlheader.vm)
Is it possible that the validation framework retrieves the properties from
the stack when an action is ModelDriven inherited ?
Cheers
Richard.



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Opensymphony-webwork mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork








------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork

Reply via email to