ICEfaces
  1. ICEfaces
  2. ICE-5750

Persistent Message(s) support required for singleSubmit/partialSubmit

    Details

    • Type: New Feature New Feature
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.0.0
    • Component/s: Framework, ICE-Components
    • Labels:
      None
    • Environment:
      ICEfaces 2.0 Glimmer w/ Sparkle components
    • Affects:
      Documentation (User Guide, Ref. Guide, etc.), Sample App./Tutorial, Compatibility/Configuration

      Description

      In order to provide the desired "partialSubmit" behavior for ICEfaces 2.0, we need a way to have the message and messages components persist messages from previously executed components into future render phases, even when that component is not executed.

      For example, say you have a form with 3 inputText components in it, each with an associated message component. Each inputText component has "partialSubmit=true, required=true" specified:
         1. Tab into inputText #1, then tab out without entering anything -> message comp. for that comp. displays "Required" error message.
         2. Tab out of inputText #2 without entering anything -> message comps. for both inputText #1 and #2 should both now display the "required" error messages (std. JSF behavior will clear the message for inputText #1 as it wasn't executed when inputText#2 was via partialSubmit).


      Note that partialSubmit in this case is equivalent to "execute=this, render=all".

        Issue Links

          Activity

          Hide
          Mark Collette added a comment -

          Switched the saving of faces messages to happen pre-render, so that they'll survive state saving, when using the state saving strategy of not keeping the view root. Also, found a deficiency in the algorithm for detecting if a component was executed, when the form's prependId property is false. Fixed that with a visitTree implementation that does not require interpretation of clientIds to determine component parentage.

          Subversion 22377

          Show
          Mark Collette added a comment - Switched the saving of faces messages to happen pre-render, so that they'll survive state saving, when using the state saving strategy of not keeping the view root. Also, found a deficiency in the algorithm for detecting if a component was executed, when the form's prependId property is false. Fixed that with a visitTree implementation that does not require interpretation of clientIds to determine component parentage. Subversion 22377
          Hide
          Mark Collette added a comment -

          Added a sample application for testing in a single form, with h: components.

          icefaces2\samples\test\messages
          Subversion 22378
          Subversion 22379

          Show
          Mark Collette added a comment - Added a sample application for testing in a single form, with h: components. icefaces2\samples\test\messages Subversion 22378 Subversion 22379
          Hide
          Mark Collette added a comment -

          Added Instructions.rtf file to the icefaces2\samples\test\messages test application, detailing the steps to take to verify the functionality.

          Subversion 22393

          Show
          Mark Collette added a comment - Added Instructions.rtf file to the icefaces2\samples\test\messages test application, detailing the steps to take to verify the functionality. Subversion 22393
          Hide
          Mark Collette added a comment -

          We should now support the typical scenarios of f:ajax and singleSubmit scenarios, inside a single form, requiring persisting of FacesMessage objects that are global and are tied to components.

          Show
          Mark Collette added a comment - We should now support the typical scenarios of f:ajax and singleSubmit scenarios, inside a single form, requiring persisting of FacesMessage objects that are global and are tied to components.
          Hide
          Mark Collette added a comment -

          Now suppress adding component messages when those messages already exist for that component. This a work-around for an issue where we're duplicating messages.

          Subversion 22841

          Show
          Mark Collette added a comment - Now suppress adding component messages when those messages already exist for that component. This a work-around for an issue where we're duplicating messages. Subversion 22841

            People

            • Assignee:
              Mark Collette
              Reporter:
              Ken Fyten
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: