Uploaded image for project: 'MyFaces Tomahawk'
  1. MyFaces Tomahawk
  2. TOMAHAWK-143

Multiple autoUpdateDataTable elements on the same page produce unexpected results

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Won't Fix
    • None
    • None
    • AutoUpdateDataTable
    • None
    • Tested on Firefox 1.0.6, Windows XP - 9/7/2005 nightly build

    Description

      For example:

      <s:autoUpdataDataTable id="table1">
      ....
      </s:autoUpdateDataTable>

      <s:autoUpdateDataTable id="table2">
      ....
      </s:autoUpdateDataTable>

      Firefox fails to render it correctly, producing some strange results. In this case, it seems to replicate the entire page within the table (especially after a certain amount of time)...

      Attachments

        1. sandbox.war
          3.68 MB
          Sh Ma

        Activity

          tom_huber Thomas Huber added a comment -

          Tested on Firefox 1.0.6, Windows XP - build 22.09.2005

          tested with two and three autoUpdateDataTable tags, also with different beans
          it is irreproducible!

          tom_huber Thomas Huber added a comment - Tested on Firefox 1.0.6, Windows XP - build 22.09.2005 tested with two and three autoUpdateDataTable tags, also with different beans it is irreproducible!
          shmafan Sh Ma added a comment -

          Hi Thomas,

          When you mean "irreproducible," are you confirming that there is a problem with multiple autoUpdateDataTable elements or are you saying that you don't see this problem? Thanks!

          shmafan Sh Ma added a comment - Hi Thomas, When you mean "irreproducible," are you confirming that there is a problem with multiple autoUpdateDataTable elements or are you saying that you don't see this problem? Thanks!
          shmafan Sh Ma added a comment -

          I probably should have noted that I'm also using Tiles... I hope that isn't causing any problems...

          shmafan Sh Ma added a comment - I probably should have noted that I'm also using Tiles... I hope that isn't causing any problems...
          shmafan Sh Ma added a comment -

          Sorry for all the extra comments... Anyway, I forgot to mention my web app server configuration:

          • Tomcat 5.5.9
          • J2SE 5.0

          I have also tried this out on MyFaces 1.1.0 and the 9/20/2005 nightly build of sandbox.jar - again, I get the same problems...

          shmafan Sh Ma added a comment - Sorry for all the extra comments... Anyway, I forgot to mention my web app server configuration: Tomcat 5.5.9 J2SE 5.0 I have also tried this out on MyFaces 1.1.0 and the 9/20/2005 nightly build of sandbox.jar - again, I get the same problems...

          I think he means he cannot reproduce your problem.

          Can you prepare a small webapp showing your problem and sending it in?

          regards,

          Martin

          mmarinschek Martin Marinschek added a comment - I think he means he cannot reproduce your problem. Can you prepare a small webapp showing your problem and sending it in? regards, Martin
          shmafan Sh Ma added a comment -

          Hi Martin,

          Thanks for the reply. I'll try to send in something, but it'll probably take a little while because of my schedule. Again, thanks for the assistance! Also, you may want to look at issue 547 again and reopen it. I'll try to send in something that might possibly reproduce that issue, too.

          shmafan Sh Ma added a comment - Hi Martin, Thanks for the reply. I'll try to send in something, but it'll probably take a little while because of my schedule. Again, thanks for the assistance! Also, you may want to look at issue 547 again and reopen it. I'll try to send in something that might possibly reproduce that issue, too.
          tom_huber Thomas Huber added a comment -

          "irreproducible" mean i cannot reproduce the problem. i tested it with J2SE 5.0 and Tomcat 5.0.28 without tiles!
          there are no problems.

          regards,
          Thomas

          tom_huber Thomas Huber added a comment - "irreproducible" mean i cannot reproduce the problem. i tested it with J2SE 5.0 and Tomcat 5.0.28 without tiles! there are no problems. regards, Thomas
          shmafan Sh Ma added a comment -

          I've attached a small sample web app that reproduces this problem. This was tested on a Windows environment (more specifically on Windows XP Pro SP2) and on Linux (Red Hat Enterprise Linux Kernel 2.6.8-1), both on X86. Both are running Tomcat 5.5.9 on Java 5. Tested using Firefox 1.0.6 and 1.0.7. It's also run on Struts 1.1 and Tiles.

          I have two examples in this attachment. One contains two tables - each table is one column. Another example also contains two table, but each table has three columns. Of signficant note are the beans for these two examples. In the source, you can tell that I force the bean thread to sleep for 0 to 1000 msec. I do this because I believe this is the probably cause of these display problems. In my own application code, the beans that are called by autoUpdateDataTable eventually make a call to a Web service (using Sun's RI of JAX-RPC). The Web service calls are certainly not instantaneous (but usually less than 1 or 2 seconds). When I introduce such uncertainty into the length of the synchronous calls, I believe it's causing some problems with the autoUpdateDataTable element. If you take the Thread.sleep() statement out, then you don't see such problems rendering the tables. Thus, I believe there may be some problems with synchronous calls that last for a fairly long time on a page with multiple autoUpdateDataTable elements (interestingly, if I only have one autoUpdateDataTable elements in my web app, I don't experience such rendering problems). Also, I just thought about this... I haven't tested my theory on a non-Tiles page yet (you may yet see this happen on a non-Tiles application), but I think I'm out of time this weekend (I was basically just deleting things from my Tiles web app), but I'll try it sooner or later...

          BTW, the problems are more easily evident in the multiple column example. I've noticed that the single column example sometimes works correctly - thus you may need to refresh the browser in order to replicate this problem. Again, I hope I'm not doing something out of the ordinary or stupid...

          shmafan Sh Ma added a comment - I've attached a small sample web app that reproduces this problem. This was tested on a Windows environment (more specifically on Windows XP Pro SP2) and on Linux (Red Hat Enterprise Linux Kernel 2.6.8-1), both on X86. Both are running Tomcat 5.5.9 on Java 5. Tested using Firefox 1.0.6 and 1.0.7. It's also run on Struts 1.1 and Tiles. I have two examples in this attachment. One contains two tables - each table is one column. Another example also contains two table, but each table has three columns. Of signficant note are the beans for these two examples. In the source, you can tell that I force the bean thread to sleep for 0 to 1000 msec. I do this because I believe this is the probably cause of these display problems. In my own application code, the beans that are called by autoUpdateDataTable eventually make a call to a Web service (using Sun's RI of JAX-RPC). The Web service calls are certainly not instantaneous (but usually less than 1 or 2 seconds). When I introduce such uncertainty into the length of the synchronous calls, I believe it's causing some problems with the autoUpdateDataTable element. If you take the Thread.sleep() statement out, then you don't see such problems rendering the tables. Thus, I believe there may be some problems with synchronous calls that last for a fairly long time on a page with multiple autoUpdateDataTable elements (interestingly, if I only have one autoUpdateDataTable elements in my web app, I don't experience such rendering problems). Also, I just thought about this... I haven't tested my theory on a non-Tiles page yet (you may yet see this happen on a non-Tiles application), but I think I'm out of time this weekend (I was basically just deleting things from my Tiles web app), but I'll try it sooner or later... BTW, the problems are more easily evident in the multiple column example. I've noticed that the single column example sometimes works correctly - thus you may need to refresh the browser in order to replicate this problem. Again, I hope I'm not doing something out of the ordinary or stupid...

          Apparently AutoUpdateDataTable is being deprecated in favor of pprPeriodicalUpdate.
          I'd recommend you switch over to using it, or join the discussion on the dev list on whether we should keep AutoUpdateDataTable.

          http://example.irian.at/example-sandbox-20070329/pprPanelGroupPeriodicalUpdate.jsf

          mkienenb Mike Kienenberger added a comment - Apparently AutoUpdateDataTable is being deprecated in favor of pprPeriodicalUpdate. I'd recommend you switch over to using it, or join the discussion on the dev list on whether we should keep AutoUpdateDataTable. http://example.irian.at/example-sandbox-20070329/pprPanelGroupPeriodicalUpdate.jsf

          People

            mmarinschek Martin Marinschek
            shmafan Sh Ma
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: