[
https://issues.apache.org/jira/browse/TRINIDAD-1129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12607072#action_12607072
]
Stephen Friedrich commented on TRINIDAD-1129:
---------------------------------------------
I don't know what exactly you mean by "myfaces' validation".
Can't we just remove the super class altogether?
I mean, checking that a value is in a range is not exactly a big deal that
justifies a dependency on other code.
Just directly implementing the validator interface would maybe add half a dozen
lines of code to the validator (probbaly less, as there's already logic that
checks all the different cases, but the "valid" case).
If that's ok with you I'll create a patch that does exactly that for all the
validators that currently extend the concrete JSF validator classes.
> Server-side validation does not work when using Sun JSF implementation
> ----------------------------------------------------------------------
>
> Key: TRINIDAD-1129
> URL: https://issues.apache.org/jira/browse/TRINIDAD-1129
> Project: MyFaces Trinidad
> Issue Type: Bug
> Affects Versions: 1.2.8-core
> Reporter: Stephen Friedrich
> Attachments: test.war
>
>
> <tr:validateLength> (and very probably other Trinidad validator also) do not
> validate anything on the server side at all.
> Trinidad's org.apache.myfaces.trinidad.validator.LengthValidator is a
> subclass of javax.faces.validator.LengthValidator.
> Trinidad's validate() method first delegates to the super class and if no
> validation exception occurs there, it does nothing.
> However the JSF base class never validates anything because the "minimum" and
> "maximum" fields do not have their values restored.
> It seems that the Trinidad way of handling state saving conflicts with
> mojarra's expectations.
> (Using mojarra 1.2_08)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
