Named validators clash

[MikeSeth]

It is impossible to have validators with the same name in both read and write contexts of an action. The validators are read linearly, and write validators override read validators with the same name. However, write validators only respond to write methods and so would not be executed by the validation manager in a read action. In other words, a read validator with the same name as a write validator would not work.

For example, in this configuration the read validation would be queried because validator names are different :

<validators method="read">

<validator class="isnotempty" name="username_present" severity="error" required="true">

<argument>username</argument>

</validator>

</validators>

<validators method="write">

<validator class="isnotempty" name="no_username" severity="error" required="true">

<argument>username</argument>

</validator>

</validators>

However, in this configuration the names are the same and so the read validator would not be executed in read context:

<validators method="read">

<validator class="isnotempty" name="no_username" severity="error" required="true">

<argument>username</argument>

</validator>

</validators>

<validators method="write">

<validator class="isnotempty" name="no_username" severity="error" required="true">

<argument>username</argument>

</validator>

</validators>

[mikeseth]

Dominik says this is principally unfixable. Validator name uniqueness is an operational constraint. The validator loading mechanism should detect duplicate validator names and raise hell.

[dominik]

(In [2124]) allow validators for different methods have the same name fixes #582

[V1P3RC0P]

 http://www.liquidkids.org/ ativan cheap generic gwnhio  http://www.lovescousin.com/ meridia rpsya  http://www.mediaspecblog.com/ accutane 8434  http://www.tennismaschile.com/tramadol.html tramadol snek