Details
-
Type:
Bug
-
Status: Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: EE-3.3.0.GA_P01
-
Fix Version/s: None
-
Component/s: PortletFacesBridge Extensions
-
Labels:None
-
Environment:WebSphere Portal Portletfaces Bridge
-
Affects:Compatibility/Configuration
Description
With WebSphere Portal, we rely on the PortletFaces Bridge. When a component sends an Ajax request it can either trigger normal or subtree rendering. During normal rendering, we rely on the ViewMap containing the previous version of the DOM which we can use to diff against the current version and generate the required updates. The problem is that the ViewMap does not currently contain the old DOM. It's unclear how far back this problem might go as the bridge hasn't been altered in some time.
Fortunately, when the old DOM is not found, we have additional fall-back logic which attempts to regenerate the entire view of the portlet and replace it. While not as efficient, it does allow WebSphere Portal to continue to work.
Fortunately, when the old DOM is not found, we have additional fall-back logic which attempts to regenerate the entire view of the portlet and replace it. While not as efficient, it does allow WebSphere Portal to continue to work.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
Documented this as a known issue in the Release Notes for EE 3.3.0.GA_P01.