Details
New Feature
Minor
Description
When multiple ICEfaces portlets are loaded on a single portal page, each portlet attempts to load it's own set of important resources - notably the JavaScript bridge. Because we dynamically modify the contents of the bridge before it is served to include specific configuration data, this multiple loading/evaluation behaviour can cause significant problems. We need to come up with a strategy for only loading the appropriate resources once per page while still allowing them to serve all the views (ie portlets) that require the functionality.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
The problem that this issue initially caused has been fixed. Loading our bridge multiple times now works so multiple portlets will operate effectively on a single page even if the bridge is downloaded multiple times. However, it would be a good optimization to allow certain shared resources like the bridge to not be downloaded more than necessary. Some I'm changing this from a Major Bug to a Minor Feature.
Show
Deryk Sinotte
added a comment - The problem that this issue initially caused has been fixed. Loading our bridge multiple times now works so multiple portlets will operate effectively on a single page even if the bridge is downloaded multiple times. However, it would be a good optimization to allow certain shared resources like the bridge to not be downloaded more than necessary. Some I'm changing this from a Major Bug to a Minor Feature.
Signifcant changes to the bridge have been made since 1.6 DR4 to support resource loading in general as well as more specifically for portlets. The bridge is now more aware of when it is loaded multiple times and we're continuing to make improvements when running portlets from separate .war files so that multiple copies of the bridge can cooperate. Resolving as fixed.