ICEfaces
  1. ICEfaces
  2. ICE-9223

Normalize the way ace:gMap handles its state

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 3.3
    • Fix Version/s: EE-3.3.0.GA, 4.0.BETA, 4.0
    • Component/s: ACE-Components
    • Labels:
      None
    • Environment:
      Any
    • Salesforce Case Reference:

      Description

      At the moment, ace:gMap has some hidden input fields that submit to the server state information like zoom level, lat, lng, etc. that the user modified by directly interacting with the map. These input fields aren't decoded in the standard way right now, but instead there's a mechanism in the Render Response phase that attempts to update the state of the component, based on the submitted values of these input fields and the old values of these attributes in the component. However, this mechanism is far from perfect, since it is not able to update the properties in the bean that are bound to these attributes, in some cases, and it fails to correctly update these attribute values in some other cases. Moreover, doing these updates in the last phase of the lifecycle can lead to problems when applications try to modify such values in the Invoke Application phase, which is the normal fashion. The right thing to do is to decode these state values in the Apply Request Values phase, as is the case with all input components.

        Activity

        Hide
        Arturo Zambrano added a comment -

        Committed improvement at revision 34743.

        Show
        Arturo Zambrano added a comment - Committed improvement at revision 34743.

          People

          • Assignee:
            Arturo Zambrano
            Reporter:
            Arturo Zambrano
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: