[
https://issues.apache.org/jira/browse/TRINIDAD-1129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12607073#action_12607073
]
Stephen Friedrich commented on TRINIDAD-1129:
---------------------------------------------
Regarding: org.apache.myfaces.trinidad.CACHE_VIEW_ROOT
That should not make any difference for server-side state saving, right?
First of all, I'd like to keep my pages small, plus the warning "template text
in Facelets may appear in duplicate" does not sound like something I'd like to
deal with.
But I'll give it a try and especially check how PPR is affected.
Thanks!
> 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.
