Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 4.2, EE-4.2.0.GA, EE-3.3.0.GA_P05
-
Fix Version/s: 4.3, EE-3.3.0.GA_P06
-
Component/s: Framework
-
Labels:None
-
Environment:ICEfaces
-
Support Case References:
-
Workaround Description:Account for the old document to be null and generate updates for the fragments pointed to by the 'javax.faces.partial.render' parameter.
Description
When a partial submit is issued from one view but the rendered view is different the old document used to calculate the differences in the page is null.
ICEfaces is normally expecting to generate a diff within the same view, not two different views, even if they both contain the same (expected to be rendered) components. This is an ICEfaces limitation. In the past we discussed the possibility of keeping the previous/old DOM in the window scope, which is the natural way, but at the time of discussion the window scope was not mature enough.
ICEfaces is normally expecting to generate a diff within the same view, not two different views, even if they both contain the same (expected to be rendered) components. This is an ICEfaces limitation. In the past we discussed the possibility of keeping the previous/old DOM in the window scope, which is the natural way, but at the time of discussion the window scope was not mature enough.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
| Repository | Revision | Date | User | Message |
| ICEsoft Public SVN Repository | #52251 | Thu Jan 25 14:35:46 MST 2018 | mircea.toma | |
| Files Changed | ||||
MODIFY
/icefaces4/trunk/icefaces/core/src/main/java/org/icefaces/impl/context/DOMPartialViewContext.java
MODIFY
/icefaces4/trunk/icefaces/core/src/main/java/org/icefaces/impl/application/PropagatingNavigationHandler.java
MODIFY
/icefaces4/trunk/icefaces/core/test.xml
|