When an IF 2 app. has the com.icesoft.faces.gmapKey context param defined in it's web.xml, the ICEfaces bridge will load the gmap bootstrap JS into the head as part of each initial page request so it is there in case the gmap component is used or dynamically introduced on that page. This is necessary to work-around a JSF issue with updating head region contents dynamically.

 <context-param>
        <param-name>com.icesoft.faces.gmapKey</param-name>
        <param-value>ABQIAAAADlu0ZiSTam64EKaCQr9eTRTOTuQNzJNXRlYRLknj4cQ89tFfpxTEqxQnVWL4k55OPICgF5_SOZE06A
        </param-value>
    </context-param>

In any case, when this param is defined, and the application inits the gmap component on the page, if the gmap key value does not match the URL/host-name for the application, the gmap JS will display an error dialog. When this occurs, it interferes with the normal loading of the rest of the ICEfaces / ACE components, etc. JS on that page.

We should investigate to see if it may be possible to load the ICEfaces JS resources first, and leave the gmap init to the end so that if it fails with the warning, it doesn't break other functionality on the page.