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.
Activity
Deryk Sinotte
created issue -
Deryk Sinotte
made changes -
Field | Original Value | New Value |
---|---|---|
Assignee | Deryk Sinotte [ deryk.sinotte ] |
Deryk Sinotte
made changes -
Issue Type | Bug [ 1 ] | New Feature [ 2 ] |
Priority | Major [ 3 ] | Minor [ 4 ] |
Deryk Sinotte
made changes -
Status | Open [ 1 ] | Resolved [ 5 ] |
Fix Version/s | 1.7DR#3 [ 10112 ] | |
Resolution | Fixed [ 1 ] |
Ken Fyten
made changes -
Fix Version/s | 1.7 [ 10080 ] |
Ken Fyten
made changes -
Status | Resolved [ 5 ] | Closed [ 6 ] |
Assignee | Deryk Sinotte [ deryk.sinotte ] |
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.