[ 
https://issues.apache.org/jira/browse/TRINIDAD-1129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12607035#action_12607035
 ] 

Stephen Friedrich commented on TRINIDAD-1129:
---------------------------------------------

Nope. Does not work for me. Strange.
Forgot to say: facelets 1.1.14

Here's my complete test page. When entering a single character in the text 
field and clicking on save, 
the action listener on the bean is called (but shouldn't of course):

------------------------------------------------------------------------------------------------------------------------------------------------

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN" 
"http://www.w3.org/TR/html4/strict.dtd";>
<html xmlns="http://www.w3.org/1999/xhtml";
      xmlns:trh="http://myfaces.apache.org/trinidad/html";
      xmlns:tr="http://myfaces.apache.org/trinidad";
        >

    <trh:head/>

    <trh:body>
        <tr:form defaultCommand="save">
            <tr:inputText label="Foo" value="#{foo.bar}">
                <tr:validateLength minimum="2"/>
            </tr:inputText>
            <tr:commandButton id="save" action="#{foo.save}" text="Save"/>
        </tr:form>

    </trh:body>
</html>

------------------------------------------------------------------------------------------------------------------------------------------------

And here's the bean:

package com.acme;

public class Test {
    private String bar;

    public String getBar() {
        return bar;
    }

    public void setBar(String bar) {
        this.bar = bar;
    }

    public String save() {
        System.out.println("Test.save: " + bar);
        return null;
    }
}

------------------------------------------------------------------------------------------------------------------------------------------------

bean configuration in faces-config.xml:

    <managed-bean>
        <managed-bean-name>foo</managed-bean-name>
        <managed-bean-class>com.acme.Test</managed-bean-class>
        <managed-bean-scope>session</managed-bean-scope>
    </managed-bean>


------------------------------------------------------------------------------------------------------------------------------------------------


My trinidad-config.xml:


<?xml version="1.0"?>
<trinidad-config xmlns="http://myfaces.apache.org/trinidad/config";>

    <client-validation-disabled>true</client-validation-disabled>

    <skin-family>texas</skin-family>

    <!-- Enable debug output here -->
    <debug-output>false</debug-output>

    <!-- Improve a4j compatibility -->
    <accessibility-mode>inaccessible</accessibility-mode>
</trinidad-config>


------------------------------------------------------------------------------------------------------------------------------------------------

Anything else that may cause this?

> 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
>
> <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.

Reply via email to