Details
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.
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.