ICEfaces
  1. ICEfaces
  2. ICE-7014

<ice:inputText> within composite components lose value if validation fails

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Won't Fix
    • Affects Version/s: EE-2.0.0.GA
    • Fix Version/s: 3.0, EE-2.0.0.GA_P01
    • Component/s: ICE-Components
    • Labels:
      None
    • Environment:
      Tomcat 7.0.14, Mojarra 2.1.2
    • Assignee Priority:
      P1
    • Affects:
      Compatibility/Configuration

      Description

      Given this example with prop:fieldset and prop:properyText being Composite Components and an ice:inputText within propertyText:

      <prop:fieldset>
      <prop:propertyText value="#{myBean.myValue}">
      <f:validateLength for="input" minimum="5"/>
      </prop:propertyText>
      </prop:fieldset>

      If validation fails, the ice:inputText within prop:propertyText loses its value if validation fails. This doesn't happen with an h:inputText.

       It also does NOT happen, if prop:fieldset is removed. So the bug actually only happens if the parent of composite component containing the ice:inputText is a composite component too.

        Activity

        Hide
        Deryk Sinotte added a comment -
        Show
        Deryk Sinotte added a comment - Opened up http://java.net/jira/browse/JAVASERVERFACES-2164 for this issue.
        Hide
        Deryk Sinotte added a comment - - edited

        I should also note that I've tested this with a recent version of MyFaces and it does not exhibit the problem. However, it possible that MyFaces may not be handling the dynamic includes correctly and is dodging the issue.

        Show
        Deryk Sinotte added a comment - - edited I should also note that I've tested this with a recent version of MyFaces and it does not exhibit the problem. However, it possible that MyFaces may not be handling the dynamic includes correctly and is dodging the issue.
        Hide
        Deryk Sinotte added a comment -

        Turns out the issue had already been reported as per (which includes a workaround):

        http://java.net/jira/browse/JAVASERVERFACES-1991

        Looks like there a number of related issues that hinge on this as well. Another developer has provided a patch in:

        http://java.net/jira/browse/JAVASERVERFACES-2040

        which indicates what looks to be a more fundamental problem with composite components in Mojarra but it has not been fixed/applied yet.

        Show
        Deryk Sinotte added a comment - Turns out the issue had already been reported as per (which includes a workaround): http://java.net/jira/browse/JAVASERVERFACES-1991 Looks like there a number of related issues that hinge on this as well. Another developer has provided a patch in: http://java.net/jira/browse/JAVASERVERFACES-2040 which indicates what looks to be a more fundamental problem with composite components in Mojarra but it has not been fixed/applied yet.
        Hide
        Adrian Gygax added a comment -

        After applying the workaround from JAVASERVERFACES-1991 I still have this problem.

        However, the workaround fixes the problem, that a textfield's content is always reset to the last valid value if you change it's content to an invalid value.

        Show
        Adrian Gygax added a comment - After applying the workaround from JAVASERVERFACES-1991 I still have this problem. However, the workaround fixes the problem, that a textfield's content is always reset to the last valid value if you change it's content to an invalid value.
        Hide
        Ken Fyten added a comment -

        This is believed to be an issue for Mojarra to resolve.

        Show
        Ken Fyten added a comment - This is believed to be an issue for Mojarra to resolve.

          People

          • Assignee:
            Deryk Sinotte
            Reporter:
            Adrian Gygax
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: