Hi everybody,
is there any way to configure the validation mechanism per action
instead than per form? And is it possible to configure this mechanism
per use case (not a global configuration)?
The project's architect decided that each use case (that includes
all the crud operations) should have just one Form class because it
would be easier to share information between the use case's
interfaces. We have interfaces with an odd layout - they present the
search form and the edit form together. This generates the following
situations concerning validation:
1. When the user press the search button, the edition fields must not
be validated.
2. When the user press other button related to edition, the search
fields (parameters) must not be validated.
We don't know how to control the validation mechanism to indicate
when each validation must occur. We tried to use the multipage
validation (search part is page 1, edit part is page 2) but it doesn't
work.
Does anyone know how to solve this problem? Thanks in advance.
Matheus Eduardo
Belo Horizonte / MG / Brazil
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
