myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Matthias Weßendorf (JIRA) <>
Subject [jira] Reopened: (TRINIDAD-1129) Server-side validation does not work when using Sun JSF implementation
Date Tue, 24 Jun 2008 04:59:45 GMT


Matthias Weßendorf reopened TRINIDAD-1129:

this doesn't sound correct, after thinking.
since setMaximum(getMaximum()) does change the way of isMaxSet in RI...
And... for some reasons, the Trinidad overridden validators have different defaults for
min/max. Should be zero.

the isMax/MinSet() we can get by something like this:
private boolean isMaximumSet()
  return _facesBean.getProperty(_MAXIMUM_KEY) != null;

will do the overhaul tomorrow or the other day.

> Server-side validation does not work when using Sun JSF implementation
> ----------------------------------------------------------------------
>                 Key: TRINIDAD-1129
>                 URL:
>             Project: MyFaces Trinidad
>          Issue Type: Bug
>    Affects Versions:  1.2.8-core
>            Reporter: Stephen Friedrich
>            Assignee: Matthias Weßendorf
>             Fix For: 1.0.9-core, 1.2.9-core
>         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.

View raw message