Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 4.0.BETA, EE-3.3.0.GA_P02
-
Fix Version/s: 4.0, EE-3.3.0.GA_P03
-
Component/s: ACE-Components
-
Labels:None
-
Environment:Any
-
ICEsoft Forum Reference:
Description
It was reported in the forum and by product support that Google Maps controls weren't showing for all components using the Google Maps API.
It's almost 100% sure that this is an issue on the Google side, since these components haven't been modified recently.
The cause seems to be the use of the edge/latest API version, which is the default when not specifying a specific version. So, in order to avoid this kind of issues in the future, here are two options. We can follow either of them or both.
1) Use an earlier, more stable gmap API version by default. Let's say 3.11, as the forum poster suggested (latest version is 3.18 at the moment).
2) Add a context parameter that we read in the GMapResourceHandler.java where users can specify a particular API version to use. The default would be to use no parameter at all, which is interpreted as the edge version.
It's almost 100% sure that this is an issue on the Google side, since these components haven't been modified recently.
The cause seems to be the use of the edge/latest API version, which is the default when not specifying a specific version. So, in order to avoid this kind of issues in the future, here are two options. We can follow either of them or both.
1) Use an earlier, more stable gmap API version by default. Let's say 3.11, as the forum poster suggested (latest version is 3.18 at the moment).
2) Add a context parameter that we read in the GMapResourceHandler.java where users can specify a particular API version to use. The default would be to use no parameter at all, which is interpreted as the edge version.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
Committed fix to 4.0 trunk at revision 42482, to 3.3 EE maintenance branch at revision 42483 for ace:gMap and at revision 42484 for ice:gMap.
The fix consists in adding the 'org.icefaces.ace.gmapVersion' context param for specifying the Google Maps API version to use. Also, now, the '3.exp' version is explicitly included in the URL when no version is specified, since JSF was adding another 'v' parameter in the URL (e.g. v=4_0_0_140828), which might have caused the problem in the first place.
Testing notes: Try using an earlier version of the Google Maps API by specifying a version in the Showcase web.xml file by adding the 'com.icesoft.faces.gmapVersion' context param. You can try versions 3.11 or 3.17, for example.
<context-param> <param-name>org.icefaces.ace.gmapVersion</param-name> <param-value>3.11</param-value> </context-param>Use the 'com.icesoft.faces.gmapVersion' context param for ice:gMap.
Verify that the maps work normally, and take a look at the HTML of the page to see that the Google Maps API resource is loaded in the <head> and its URL includes the version specified. Also, verify that the version in the URL is '3.exp' when the context param is not specified or when it's empty.
More information regarding Google Maps API versions can be found here: https://developers.google.com/maps/documentation/javascript/reference