Details
Description
When an ICEfaces application is initially displayed or the Content Cache is cleared, the following exception may be thrown during iceSubmit()
couldn't find container for property: bridge
Mircea, what initialization steps need to take place for the "bridge" property to exist?
This may be a browser bug, but it may also be desirable to find a workaround (such as an attempt to reinitialize the bridge).
It does not appear to occur on the simulator.
Activity
Ted Goddard
created issue -
Ted Goddard
made changes -
Field | Original Value | New Value |
---|---|---|
Assignee | Mircea Toma [ mircea.toma ] |
Ted Goddard
made changes -
Fix Version/s | 1.8DR#2 [ 10142 ] |
Repository | Revision | Date | User | Message |
ICEsoft Public SVN Repository | #17869 | Thu Nov 06 08:17:03 MST 2008 | ted.goddard | ignoring backbutton failure on BlackBerry ( |
Files Changed | ||||
MODIFY
/icefaces/trunk/icefaces/bridge/src/synchronizer.js
|
Ted Goddard
made changes -
Status | Open [ 1 ] | Resolved [ 5 ] |
Resolution | Fixed [ 1 ] |
Ken Fyten
made changes -
Fix Version/s | 1.8 [ 10161 ] |
Ken Fyten
made changes -
Status | Resolved [ 5 ] | Closed [ 6 ] |
Assignee | Mircea Toma [ mircea.toma ] |
In application.js the following change:
try
{ var documentSynchronizer = new Ice.Document.Synchronizer(window.logger, sessionID, viewID); }catch (e)
{ alert("synchronizer " + e); }occasionally displays
"synchronizer Same-origin policy violation", so perhaps the history iframe is in a strange state due to not being cached.
Mircea, what problems would arise if the documentSynchronizer was not initialized? A sufficient workaround may be to catch the above exception and log it; at least the bridge would otherwise initialize.