ICEfaces
  1. ICEfaces
  2. ICE-4474

CLONE -inputFile component disappearing

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Won't Fix
    • Affects Version/s: 1.8
    • Fix Version/s: 1.8.1
    • Component/s: ICE-Components
    • Labels:
      None
    • Environment:
      ICEfaces 1.8 final, IE8, FF3.
    • Workaround Exists:
      Yes
    • Workaround Description:
      Hide
      As a workaround, try spawning a thread to process any potentially long-lasting operations instead of doing that in your actionListener. Then when you're done your processing, just kick off a server push to update the display.
      Show
      As a workaround, try spawning a thread to process any potentially long-lasting operations instead of doing that in your actionListener. Then when you're done your processing, just kick off a server push to update the display.

      Description

      This JIRA is a follow-on to an original issue believed resolved for 1.8.0 (ICE-3912).

      It seems that in some cases the issue still occurs on FF3 (comments copied from ICE-3912, which is closed since it released with 1.8):

      Chad Brandon added a comment - 07/May/09 06:12 PM
      This issue doesn't appear to be fixed. I'm using 1.8.0 and I'm seeing the inputFile html disappear. It doesn't happen all the time, but seems to happen almost always when the method that does the upload takes 30 seconds or more to complete.

      Mark Collette added a comment - 07/May/09 06:25 PM
      Chad, which browser and version are you using? Is you internet connection stalling, or is the file just really large?

      Chad Brandon added a comment - 07/May/09 06:33 PM
      Thanks for the quick response Mark. The file is actually fairly small. But once I upload the file I run a process on it that takes about 30 seconds right after. The html seems to disappear about 2-5 seconds into the process (again not always, but most of the time; probably 3 out of 4 times). It happens in both firefox 3.0.10 and IE 8. Looking at the resulting html using firebug when the upload widget disappears I can see that the iframe that contains the component's contents no longer contains the html that it did before it disappeared.

      Chad Brandon added a comment - 07/May/09 06:42 PM
      Just another note: the progress indicator correctly shows that the file was uploaded fine once the method completes, its just the inputFile component that completely disappears.

        Activity

        Hide
        Mark Collette added a comment -

        As a workaround, try spawning a thread to process your file, instead of doing that in your actionListener. Then when you're done your processing, just kick off a server push to update the display.

        Show
        Mark Collette added a comment - As a workaround, try spawning a thread to process your file, instead of doing that in your actionListener. Then when you're done your processing, just kick off a server push to update the display.
        Hide
        Chad Brandon added a comment -

        Thanks Mark, I'll try that.

        Show
        Chad Brandon added a comment - Thanks Mark, I'll try that.
        Hide
        Mark Collette added a comment -

        I can comfirm that large files were not an issue. But, putting a 10 second delay in my actionListener showed me that FF3, IE6, Opera and Safari all showed the inputFile disappear after 5 seconds of delay.

        Show
        Mark Collette added a comment - I can comfirm that large files were not an issue. But, putting a 10 second delay in my actionListener showed me that FF3, IE6, Opera and Safari all showed the inputFile disappear after 5 seconds of delay.
        Hide
        Mark Collette added a comment -

        All browsers behave the same, in that they give up on rendering the returned iframe content if the actionListener takes over 5 seconds. The actionListener should instead be coded to kick off a worker thread, and return immediately. The worker thread can do a server push, when it's done, if necessary.

        Show
        Mark Collette added a comment - All browsers behave the same, in that they give up on rendering the returned iframe content if the actionListener takes over 5 seconds. The actionListener should instead be coded to kick off a worker thread, and return immediately. The worker thread can do a server push, when it's done, if necessary.
        Hide
        Mark Collette added a comment -

        Mention this in the TLD for inputFile's action and actionListener attributes.

        Subversion 18878
        icefaces\component-metadata\src\main\resources\conf\ice_cust_properties\cust-inputFile-props.xml

        Show
        Mark Collette added a comment - Mention this in the TLD for inputFile's action and actionListener attributes. Subversion 18878 icefaces\component-metadata\src\main\resources\conf\ice_cust_properties\cust-inputFile-props.xml
        Hide
        GA A added a comment -

        Could you elaborate on the workaround please.

        I face similar issue in Windows VISTA + IE8. I use icefaces 1.8.0. Tried even with 1.8.1. Still fails.

        Also, I have a preview option which works fine in IE7, but does not work in IE8 as page/section does not get refreshed.

        BTW, if it helps, I run this icefaces code in a portlet.

        Show
        GA A added a comment - Could you elaborate on the workaround please. I face similar issue in Windows VISTA + IE8. I use icefaces 1.8.0. Tried even with 1.8.1. Still fails. Also, I have a preview option which works fine in IE7, but does not work in IE8 as page/section does not get refreshed. BTW, if it helps, I run this icefaces code in a portlet.
        Hide
        Bruno Almeida added a comment -

        Hi Mark,

        Can you please source us with the workaround. I'm quite newbie with icefaces and I'm facing this problem. I'm having dificulties to translate into code "spawning a thread to process your file, then when you're done your processing, just kick off a server push to update the display".

        Thanks in advance for your help.

        Show
        Bruno Almeida added a comment - Hi Mark, Can you please source us with the workaround. I'm quite newbie with icefaces and I'm facing this problem. I'm having dificulties to translate into code "spawning a thread to process your file, then when you're done your processing, just kick off a server push to update the display". Thanks in advance for your help.

          People

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

            Dates

            • Created:
              Updated:
              Resolved: