ICEfaces
  1. ICEfaces
  2. ICE-9267

ace:fileEntry - Add ability to disable the message persistance

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: EE-3.2.0.GA, 3.3
    • Fix Version/s: EE-3.3.0.GA, 4.0.BETA, 4.0
    • Component/s: ACE-Components
    • Labels:
      None
    • Environment:
      All
    • Assignee Priority:
      P1
    • Salesforce Case Reference:
    • Affects:
      Compatibility/Configuration

      Description

      Feature Request: Add an attribute that will allow a developer to choose if the messages displayed by the ace:fileEntry can be persisted on subsequent submits/updates. Currently the messages will stay on the screen while a fileEntry component is on the page.

        Issue Links

          Activity

          Hide
          Ken Fyten added a comment -

          Marking Invalid as the correct fix for the customer issue is ICE-9276.

          Show
          Ken Fyten added a comment - Marking Invalid as the correct fix for the customer issue is ICE-9276 .
          Hide
          Ken Fyten added a comment -

          Re-opening as this now seems valid for cases where applications don't want fileEntry success or failure messages to display on subsequent updates.

          Show
          Ken Fyten added a comment - Re-opening as this now seems valid for cases where applications don't want fileEntry success or failure messages to display on subsequent updates.
          Hide
          Mark Collette added a comment -

          Without this feature, or having it set to true, this is the existing behaviour:

          If there is a failure condition, like maxFileSize, then the faces message for that will be shown on the lifecycle of the actual upload. Same for a success message. Then, if required=false, on subsequent non-uploading executes, those same messages will keep being re-added, but if required=true, then they will not, and the required message will instead be added.

          So with messagePersistence set to false, when required=false, the success/failure messages will not be re-added on subsequent executes, and with required=true, the required message will never be shown.

          Show
          Mark Collette added a comment - Without this feature, or having it set to true, this is the existing behaviour: If there is a failure condition, like maxFileSize, then the faces message for that will be shown on the lifecycle of the actual upload. Same for a success message. Then, if required=false, on subsequent non-uploading executes, those same messages will keep being re-added, but if required=true, then they will not, and the required message will instead be added. So with messagePersistence set to false, when required=false, the success/failure messages will not be re-added on subsequent executes, and with required=true, the required message will never be shown.
          Hide
          Mark Collette added a comment -

          Added messagePersistence property, with default value of true, so that apps can disabled messages being re-added on subsequent executes of FileEntry after an upload.

          icefaces3 trunk
          Subversion 36175

          icefaces EE 3.3 GA tag branch
          Subversion 36176

          Show
          Mark Collette added a comment - Added messagePersistence property, with default value of true, so that apps can disabled messages being re-added on subsequent executes of FileEntry after an upload. icefaces3 trunk Subversion 36175 icefaces EE 3.3 GA tag branch Subversion 36176
          Hide
          Mark Collette added a comment -

          Spun off issues with required into follow-up task ICE-9343.

          Show
          Mark Collette added a comment - Spun off issues with required into follow-up task ICE-9343 .

            People

            • Assignee:
              Mark Collette
              Reporter:
              Arran Mccullough
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: