Arturo Zambrano added a comment - 22/Nov/12 10:10 PM - edited After extensive investigation, I finally found out that the problem has nothing to do with the mandatory resource configuration, and that the problem is caused the the google code itself. This situation only happens when trying to load a gmap component dynamically, as the gMapMandResConf.jsf page does: it dynamically includes an xhtml document, containing a gmap, when the checkbox is on. When the script snippet produced by the renderer to initialize the component is loaded to the page via a dynamic update, the google maps API fails to work properly. In particular, it fails to download a number of required javascript resources required for gmaps to work. If the script to initialize the component is already present when the page is first loaded, then the google API successfully loads all other required resources from google's servers and the map is displayed. For now, the solution seems to be to initialize a dummy map when first loading the page, and then discarding it. This causes the gmaps API to (pre)load all external required resources as soon as the page is loaded. If the following code is either hard-coded in a script element on the page or added to the end of the gmap component scripts, it will solve the issue: new google.maps.Map(document.createElement('div'), {mapTypeId:google.maps.MapTypeId.ROADMAP, zoom:5, center: new google.maps.LatLng(0,0)} );

Arturo Zambrano added a comment - 04/Dec/12 11:01 PM - edited Committed fix to trunk at revision 32334. The fix consisted in normalizing the API resource registration in order to prevent the browser from requesting the resource again, causing incorrect behaviour in the client.