-
Type: Improvement
-
Status: Resolved
-
Priority: Minor
-
Resolution: Won't Fix
-
Affects Version/s: 6.0
-
Fix Version/s: None
-
Component/s: Performance, Seam / JSF UI
-
Epic Link:
-
Tags:
-
Team:AT
-
Sprint:nxAT Sprint 8.2.1
-
Story Points:2
There is a helper JSF function nxu:componentAbsoluteId that resolves an absolute id given a component for anchor in the tree, and a "local" id.
Current lookup strategy looks for a component with this id under the given component anchor, and spreads the search to its parent naming containers if not found.
This allows to locate components in a given "region" of the tree.
If search needs to be spread to parent naming containers, children that have already already been browsed should not be taken into account after that.
- is required by
-
NXP-15050 Investigate performance issue (CPU overload) on JSF2 branch
- Resolved
-
NXP-15757 Clicking Select all should enable document list toolbar actions
- Resolved
-
NXP-15341 Fix ajax render in content views, saved searches and fancyboxes
- Resolved
-
NXP-17370 Large ContentViews are abnormally slow
- Resolved