Background.... I have a Struts 1.1 application, one view has 2 JSP's that do the following:
Parent JSP (hereafter JSP#1) has a nested iFrame on the top half of the screen that contains child JSP (hereafter JSP#2).
Each record in the result set on child JSP#2 has an 'EDIT' link.
JSP#1 contains all the edit controls, so when a user clicks the 'EDIT' link beside a record on nested JSP#2, we submit to an action servlet that reloads the page with the record's data loaded into the edit fields on parent JSP#1.
The nested iFrame was required so when JSP#2 auto-refreshes, it would not interrupt users editing data in the bottom part of parent JSP#1.
Works like a charm (or at least as a webapp is expected to) in my opinion ... However my users do not agree.
My main Problem: When the nested JSP#2 refreshes, the content of the iFrame flickers -- which seems to be a REALLY big annoyance. IE page refresh is noticeably worse than on FireFox/Navigator but "corporate" policy demands IE so changing browsers is out. This problem must be fixed -- they want a "flickerless" data refresh (keeping in mind the database is halfway across the country from the users).
What I have planned to attempt to please the masses:
Changing the iFrame containing JSP#2 to a hidden form object so refreshes are in the background. Stripped all formatting and the 'EDIT' link.
Cloned the scrollable <div> result set onto JSP#1 (including EDIT link), so the list and edit fields are no longer on different pages.
- The result set lists are defined as java.util.Collection - Each element in these Collections are DynaActionForms
This is my form bean definition from my struts-cfg.xml
.. and here is how the result set is set up to loop through this Collection of DynaActionForms to produce the result set:
Any help or tips would be appreciated.
[ July 25, 2006: Message edited by: Jitwad ] [ July 25, 2006: Message edited by: Jitwad ]