Mailing-List: contact dev-help@myfaces.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "MyFaces Development" <dev@myfaces.apache.org>
Message-ID: <1913033482.1214277225120.JavaMail.jira@brutus>
Date: Mon, 23 Jun 2008 20:13:45 -0700 (PDT)
From: =?utf-8?Q?Matthias_We=C3=9Fendorf_=28JIRA=29?= <dev@myfaces.apache.org>
To: dev@myfaces.apache.org
Subject: [jira] Resolved: (TRINIDAD-1129) Server-side validation does not
 work when using Sun JSF implementation
In-Reply-To: <1669149395.1213950825042.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/TRINIDAD-1129?page=3Dcom.atlas=
sian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matthias We=C3=9Fendorf resolved TRINIDAD-1129.
------------------------------------------

       Resolution: Fixed
    Fix Version/s: 1.2.9-core
                   1.0.9-core

I did the proposed "fix" in restoreState().
By that way we can keep the specified validation logic.
Any update of a new JSF spec version allows us to reuse the specified logic=
.

The other was was get rid of super.validate() and do the validation ourself=
.
But that would make the super-class kinda needless.

But we want to keep the instance of javax.faces...., therefore I am doing t=
his
extra call in the restoreState()...

> 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
>            Assignee: Matthias We=C3=9Fendorf
>             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 sub=
class 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 mo=
jarra's expectations.
> (Using mojarra 1.2_08)

--=20
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.