ICEfaces
  1. ICEfaces
  2. ICE-1346

The InputFile Component with OutputProgress Component demo doesn't update/rerender in the browser with fast HTTP connections

          Details

          • Type: Bug Bug
          • Status: Closed
          • Priority: Major Major
          • Resolution: Fixed
          • Affects Version/s: 1.5.3
          • Fix Version/s: 1.6DR#4, 1.6
          • Component/s: ICE-Components
          • Labels:
            None
          • Environment:
            Windows XP / Tomcat 5.5.17

            Description

            The InputFile Component with OutputProgress Component demo (http://facestutorials.icefaces.org/tutorial/inputFile-tutorial.html#progressinputfilecomponent) works great when there is slow (non-instant) connectivity between browser and server, but say, when testing on localhost with Tomcat, the <ice:outputProgress> component and <ice:outputMessage> component do not get updated in the browser.

              Activity

              Ascending order - Click to sort in descending order
              Hide
              Permalink
              Mark Collette added a comment -

              There also a forum posting, from someone else about this:
              http://www.icefaces.org/JForum/posts/list/4389.page

              Show
              Mark Collette added a comment - There also a forum posting, from someone else about this: http://www.icefaces.org/JForum/posts/list/4389.page
              Hide
              Permalink
              Mark Collette added a comment -

              Turns out that progress notifications can start coming in from the commons-upload code before commons-upload tells us which component to send those notifications to. In the case of a small file being uploaded, all of the notifications came in before we knew who to forward them to, effectively losing them all. Now we don't lose them anymore.

              Subversion 13833
              icefaces\core\src\com\icesoft\faces\webapp\http\servlet\UploadServlet.java
              icefaces\component\src\com\icesoft\faces\component\inputfile\InputFile.java

              Show
              Mark Collette added a comment - Turns out that progress notifications can start coming in from the commons-upload code before commons-upload tells us which component to send those notifications to. In the case of a small file being uploaded, all of the notifications came in before we knew who to forward them to, effectively losing them all. Now we don't lose them anymore. Subversion 13833 icefaces\core\src\com\icesoft\faces\webapp\http\servlet\UploadServlet.java icefaces\component\src\com\icesoft\faces\component\inputfile\InputFile.java
              Hide
              Permalink
              Mark Collette added a comment -

              Fixed a few issues when uploading too large of a file or no file or a bogus file, with cleaning out old state.

              Subversion 13854
              icefaces\core\src\com\icesoft\faces\webapp\http\servlet\UploadServlet.java
              icefaces\component\src\com\icesoft\faces\component\inputfile\InputFile.java

              Show
              Mark Collette added a comment - Fixed a few issues when uploading too large of a file or no file or a bogus file, with cleaning out old state. Subversion 13854 icefaces\core\src\com\icesoft\faces\webapp\http\servlet\UploadServlet.java icefaces\component\src\com\icesoft\faces\component\inputfile\InputFile.java

                People

                • Assignee:
                  Unassigned
                  Reporter:
                  Neil Griffin
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  0 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: