ICEfaces
  1. ICEfaces
  2. ICE-6372

fileEntry interferes with form post

          Details

          • Type: Bug Bug
          • Status: Closed
          • Priority: Major Major
          • Resolution: Fixed
          • Affects Version/s: 2.0-Beta2
          • Fix Version/s: 2.0.1
          • Component/s: Bridge
          • Labels:
            None
          • Environment:
            ICEfaces

            Description

            If ace-showcase is modified so that fileEntryInclude.xhtml makes use of a single form, the file deletion does not function.
            If h:commandButton is replaced with h:pushButton, then the delete operation is successful. This is likely due to interference of the fileEntry Ajax mechanism (pushButton uses the Ajax APIs directly).

              Activity

              Ascending order - Click to sort in descending order
              Hide
              Permalink
              Ken Fyten added a comment -

              Needs retesting on trunk.

              Show
              Ken Fyten added a comment - Needs retesting on trunk.
              Hide
              Permalink
              Mark Collette added a comment -

              When the delete h:commandButton is in the same form, these are the scenarios and their results:

              h:commandButton with f:setPropertyActionListener : Does a standard full form post, which re-uploads the last selected file and correctly processed the post response.

              h:commandButton with f:param : Does an ajax form post, which does not upload anything, and gets back a full document response, which it now correctly updates the page with, although that causes it to re-GET all of the CSS and Javascript.

              ace:pushButton with f:param and with f:setPropertyActionListener : Does an ajax form post, which does not upload anything, and gets back partial updates, which it correctly updates the page with.

              Show
              Mark Collette added a comment - When the delete h:commandButton is in the same form, these are the scenarios and their results: h:commandButton with f:setPropertyActionListener : Does a standard full form post, which re-uploads the last selected file and correctly processed the post response. h:commandButton with f:param : Does an ajax form post, which does not upload anything, and gets back a full document response, which it now correctly updates the page with, although that causes it to re-GET all of the CSS and Javascript. ace:pushButton with f:param and with f:setPropertyActionListener : Does an ajax form post, which does not upload anything, and gets back partial updates, which it correctly updates the page with.
              Hide
              Permalink
              Mark Collette added a comment -

              From the component perspective, clearing the file selection after a successful upload would be a good way to avoid duplicate uploads: ICE-6535

              Show
              Mark Collette added a comment - From the component perspective, clearing the file selection after a successful upload would be a good way to avoid duplicate uploads: ICE-6535

                People

                • Assignee:
                  Mark Collette
                  Reporter:
                  Ted Goddard
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  0 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: