Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: EE-4.3.0.GA_P02
-
Fix Version/s: EE-4.3.0.GA_P03, EE-3.3.0.GA_P09
-
Component/s: ACE-Components
-
Labels:None
-
Environment:Any
-
ICEsoft Forum Reference:
Description
If an ace:tabset with clientSide="false" contains a tab pane with cache="none" and that pane is not loaded by default upon loading the page, the beans used in that pane shouldn't be initialized on page load. This is not the case when such pane contains an ace:datatable with lazy loading. The beans used by the lazy loaded data table shouldn't be initialized on page load but until the tab that contains it is activated in the tab set. It is being initialized on page load right now however. If the table is not lazy loaded, then its beans don't get initialized on page load but until the tab that contains it is activated, as expected. So, it's only a problem with lazy tables.
The problem for the non-lazy case was fixed as perICE-11239.
The problem for the non-lazy case was fixed as per
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
r53366: Applied fix to the EE 3.3 maintenance branch.
Show
Arturo Zambrano
added a comment - r53366: Applied fix to the EE 3.3 maintenance branch.
r53366: Only load the lazy data, for the purposes of visiting rows, if this is an update and not a first rendering.
Show
Arturo Zambrano
added a comment - r53366: Only load the lazy data, for the purposes of visiting rows, if this is an update and not a first rendering.
r53408: Refactor the calls to loadLazyData() to outside of the visit tree logic, so that the lazy data is only loaded when the component is actually executed and/or rendered, thus preventing loading the lazy data when the component is not visible (4.3 EE maintenance branch).
r53409: Committed fix to 4.3 P03 tag.