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