Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: 2.0-Beta2
-
Fix Version/s: 2.0.0
-
Component/s: ACE-Components, Framework
-
Labels:None
-
Environment:client
-
ICEsoft Forum Reference:
Description
JS error occurs when loading a page that references JS resources defined by icefaces-ace-2.0-Beta2.jar:
"Error in extras bootstrap [TypeError: window.logger.child is not a function] "
"Error in extras bootstrap [TypeError: window.logger.child is not a function] "
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
Mircea, we believe this extraneous logger reference that you moved into YUI3 namespace was intended to enable the regular icefaces bridge console to work. If this is not the case, then please remove this code altogether.
Comps team will use either the normal IF bridge console/debugger or the YUI debugger component in the future.
Show
Ken Fyten
added a comment - Mircea, we believe this extraneous logger reference that you moved into YUI3 namespace was intended to enable the regular icefaces bridge console to work. If this is not the case, then please remove this code altogether.
Comps team will use either the normal IF bridge console/debugger or the YUI debugger component in the future.
Removed temporary logger.
Show
Mircea Toma
added a comment - Removed temporary logger.
This issue is caused by the component.js resource included by icefaces-ace-*.jar library. The file declares a global 'logger' variable which depending on the order the JS resources are loaded would overwrite the global 'logger' variable declared in icefaces-compat.jar. The 'logger' variable declared doesn't match the API and functionality of the other 'logger' variable in icefaces-compat.jar, hence the JS error.
The solution was to attach the 'logger' variable in component.js to the ice.yui3 namespace to avoid the naming conflict.