[
https://issues.apache.org/jira/browse/TRINIDAD-1129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12607059#action_12607059
]
Matthias Weßendorf commented on TRINIDAD-1129:
----------------------------------------------
these classes were overridden for two reasons:
-optimization of state-saving
-poor messages (wasn't possible to customize in the past).
I think I will do something like this in the restoreState() of these validators:
public void restoreState(FacesContext context, Object state)
{
_facesBean.restoreState(context, state);
super.setMaximum(getMaximum());
super.setMinimum(getMinimum());
}
> 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.
