ICEfaces
  1. ICEfaces
  2. ICE-5720

New singleSubmit feature for ACE components

    Details

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

      Description

      For ICEfaces 2.0 Sparkle components we require a successor to the ICEfaces 1.8 components "partialSubmit" feature to allow ease of validation and processing of form elements as they are entered by the user.

      Current thinking is to have a "partialSubmit/singleSubmit/autoSubmit" boolean attribute on each input component. When set to 'true', a value change on that component would submit the form that the component resides in with the equivalent of an f:ajax "execute=this, render=all".

      The intention is to have validation and processing be performed on that input component alone, while rendering the whole component tree so that any other components who's state's may change as a result of the value change on the component (e.g. message component) are rendered.

      It is not clear at this time of this alone will be sufficient, as there is a concern that any validation error messages from previous autoSubmits may be lost when a subsequent autoSubmit occurs on a different component, as even though the original component may remain in an invalid state, without being executed no events would fire to populate the messages components, etc. It may be necessary to also provide an enhanced version of the messages components that would cache previous messages and remove them if the source component was either no longer in the component tree, there but not rendered, or no longer invalid.

        Issue Links

          Activity

          Ken Fyten created issue -
          Ken Fyten made changes -
          Field Original Value New Value
          Salesforce Case []
          Fix Version/s 2.0-Alpha3 [ 10032 ]
          Affects [Documentation (User Guide, Ref. Guide, etc.), Sample App./Tutorial, Compatibility/Configuration]
          Assignee Priority P2
          Assignee Arturo Zambrano [ artzambrano ]
          Hide
          Arturo Zambrano added a comment -

          attached test app...

          This is the current bahavior...

          • When tabbing out of an input component, its individual message is displayed, and the global message component also displays the same validation message.
          • The global messages component only shows one validation error at a time--the one related to the last element that produced a validation error
          • When the messages are displayed all focus is lost from the page... i.e.no single element is focused.
          Show
          Arturo Zambrano added a comment - attached test app... This is the current bahavior... When tabbing out of an input component, its individual message is displayed, and the global message component also displays the same validation message. The global messages component only shows one validation error at a time--the one related to the last element that produced a validation error When the messages are displayed all focus is lost from the page... i.e.no single element is focused.
          Arturo Zambrano made changes -
          Attachment ice_se_test.war [ 12348 ]
          Arturo Zambrano made changes -
          Attachment ice_se_test.war [ 12348 ]
          Hide
          Arturo Zambrano added a comment -

          attached updated test app with message components surrounded by an <h:panelGroup> component...

          • the focus issue is not present anymore
          • among the individual <h:message> components, there is only one message visible at a time, which corresponds to the latest error message... for example, the first input field has focus, then you tab out, and the error message for the first input field is displayed... now, the second input field has focus, if you tab out, the message for the first input field disappears, and the message for the second input field is displayed... and so on...
          Show
          Arturo Zambrano added a comment - attached updated test app with message components surrounded by an <h:panelGroup> component... the focus issue is not present anymore among the individual <h:message> components, there is only one message visible at a time, which corresponds to the latest error message... for example, the first input field has focus, then you tab out, and the error message for the first input field is displayed... now, the second input field has focus, if you tab out, the message for the first input field disappears, and the message for the second input field is displayed... and so on...
          Arturo Zambrano made changes -
          Attachment ice_se_test.war [ 12350 ]
          Ken Fyten made changes -
          Link This issue depends on ICE-5750 [ ICE-5750 ]
          Hide
          Ken Fyten added a comment -

          Okay, new JIRA created for the enhanced message(s) component behavior issue (ICE-5750), linked to this one.

          Show
          Ken Fyten added a comment - Okay, new JIRA created for the enhanced message(s) component behavior issue ( ICE-5750 ), linked to this one.
          Ken Fyten made changes -
          Fix Version/s 2.0-Beta [ 10231 ]
          Fix Version/s 2.0-Alpha3 [ 10032 ]
          Ken Fyten made changes -
          Salesforce Case []
          Assignee Arturo Zambrano [ artzambrano ] Mark Collette [ mark.collette ]
          Ken Fyten made changes -
          Link This issue depends on ICE-5880 [ ICE-5880 ]
          Hide
          Ken Fyten added a comment -

          New JIRA linked to this case, ICE-5880, for new comp. to define default partialSubmit value for an entire form.

          Show
          Ken Fyten added a comment - New JIRA linked to this case, ICE-5880 , for new comp. to define default partialSubmit value for an entire form.
          Ken Fyten made changes -
          Fix Version/s 2.0-Beta2 [ 10242 ]
          Fix Version/s 2.0-Beta1 [ 10231 ]
          Ken Fyten made changes -
          Assignee Priority P2 P1
          Ken Fyten made changes -
          Security Private [ 10001 ]
          Ken Fyten made changes -
          Summary New partialSubmit feature for Sparkle components New singleSubmit feature for ACE components
          Salesforce Case []
          Component/s Framework [ 10013 ]
          Component/s Components [ 10012 ]
          Affects [Documentation (User Guide, Ref. Guide, etc.), Sample App./Tutorial, Compatibility/Configuration] [Documentation (User Guide, Ref. Guide, etc.), Sample App./Tutorial]
          Assignee Priority P1
          Hide
          Ken Fyten added a comment -

          Complete. Feature is renamed to 'singleSubmit' as it is distinctly different from the old 'partialSubmit' feature in 1.x.

          Show
          Ken Fyten added a comment - Complete. Feature is renamed to 'singleSubmit' as it is distinctly different from the old 'partialSubmit' feature in 1.x.
          Ken Fyten made changes -
          Status Open [ 1 ] Resolved [ 5 ]
          Resolution Fixed [ 1 ]
          Ken Fyten made changes -
          Fix Version/s 2.0.0 [ 10230 ]
          Ken Fyten made changes -
          Status Resolved [ 5 ] Closed [ 6 ]

            People

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

              Dates

              • Created:
                Updated:
                Resolved: