Details
Bug
Description
Once the item has been chosen and the value changed event has fired, the update returns and is applied. My guess is that the script update that comes back and is evaluated is handled differently by MyFaces and results in another full submit. The candidate area may be here (Ice.GoogleMap.submitEvent):
locateAddress: function(clientId, address) {
var gLatLng = function(point) {
if (!point) {
alert(address + ' not found');
} else {
var gmapWrapper = Ice.GoogleMap.getGMapWrapper(clientId);
if (gmapWrapper) {
gmapWrapper.getRealGMap().setCenter(point, 13);
var marker = new GMarker(point);
gmapWrapper.getRealGMap().addOverlay(marker);
marker.openInfoWindowHtml(address);
gmapWrapper.geoMarker = marker;
gmapWrapper.geoMarkerAddress = address;
Ice.GoogleMap.submitEvent(clientId, gmapWrapper.getRealGMap(), "geocoder");
} else {
//FOR IS DEFINED BUT MAP IS NOT FOUND,
//LOGGING CAN BE DONE HERE
}
} //outer if
}; //function ends here
var geocoder = Ice.GoogleMap.getGeocoder(clientId);
geocoder.getLatLng(address, gLatLng);
},
Note that adding an address manually to the inputText and hitting Enter does not result in the looping request behaviour.
Issue Links
- blocks
-
ICE-5868
MyFaces 2 compatibility
-
- Closed
-
Activity
| Field | Original Value | New Value |
|---|---|---|
| Salesforce Case | [] | |
| Assignee | Deryk Sinotte [ deryk.sinotte ] |
| Salesforce Case | [] | |
| Affects Version/s | 2.0.2 [ 10273 ] |
When debugging the network event running under Mojarra, I see two request/responses to the application. The responses only differ in one respect, the first line of JavaScript to eval. In the first response to return, the first line to eval from the request to http://localhost:8080/cs-mo/showcase.jsf is:
Ice.GoogleMap.locateAddress('iceform:gmap', 'Sao Paulo');
In the second request to http://localhost:8080/cs-mo/showcase.jsf:
Ice.GoogleMap.getGMapWrapper('iceform:gmap').getRealGMap().setZoom(13);
With MyFaces, the first request to http://localhost:8080/cs-my/showcase.jsf returns the locateAddress call:
Ice.GoogleMap.locateAddress('iceform:gmap', 'Sao Paulo');
However the second request http://localhost:8080/cs-my/showcase.jsf also contains the locateAddress call:
Ice.GoogleMap.locateAddress('iceform:gmap', 'Sao Paulo');
Looking at the GMap class where it decides what to add to the response, the encodeBegin method checks a number of values to see the state:
if ((isLocateAddress() || !initilized) && (getAddress() != null
&& getAddress().length() > 2))
else {
if (isLocatedByGeocoder(context))
else {
In this case, it's the "initilized" value that is always false due to some subtlety of state-saving. In fact, it appears saveState and restoreState are not called at all when running under MyFaces.
| Salesforce Case | [] | |
| Assignee Priority | P1 |
Looks like some recent changes might have fixed this. Not sure what but likely related to proper handling of ViewState values in forms. In any event, the GMap component appears to be working properly now. Resolving as fixed.
| Status | Open [ 1 ] | Resolved [ 5 ] |
| Resolution | Fixed [ 1 ] |
| Fix Version/s | 2.1-Beta2 [ 10294 ] |
| Status | Resolved [ 5 ] | Closed [ 6 ] |
Linking to parent MyFaces 2 compatibility JIRA.