ICEfaces
  1. ICEfaces
  2. ICE-11369

problem with dynamic update when using <ace:gMapMarker> with <ace:gMapInfoWindow>

          Details

          • Type: Bug Bug
          • Status: Closed
          • Priority: Major Major
          • Resolution: Fixed
          • Affects Version/s: EE-4.2.0.GA
          • Fix Version/s: EE-3.3.0.GA_P06
          • Component/s: ACE-Components
          • Labels:
            None
          • Environment:
            ace jsf2.2

            Description

            Please see the attached project and war. Note that when modifying the component with the ace:checkboxButton dynamically, the info Windows either do not behave at all or behave eratically.

              Activity

              Ascending order - Click to sort in descending order
              Hide
              Permalink
              Judy Guglielmin added a comment -

              war and maven project

              Show
              Judy Guglielmin added a comment - war and maven project
              Hide
              Permalink
              Ken Fyten added a comment -

              Reminder that any fix for this might be required on the 3.3 maintenance branch as well.

              Show
              Ken Fyten added a comment - Reminder that any fix for this might be required on the 3.3 maintenance branch as well.
              Hide
              Permalink
              Arturo Zambrano added a comment -

              r52032: added mechanism to update existing marker objects in the client, instead of removing them and creating new ones, in order to persist even listeners, especially those related to info windows associated with a specific marker
              r52033: committed fix to the 3.3 EE maintenance branch.

              The issue didn't have to do with an update in the Google Maps code, as initially suspected. The issue had to do with our code, which removes a marker before recreating it again when it's updated. This fix is to persist the same instance in the client, which may be already registered with various event listeners.

              Show
              Arturo Zambrano added a comment - r52032: added mechanism to update existing marker objects in the client, instead of removing them and creating new ones, in order to persist even listeners, especially those related to info windows associated with a specific marker r52033: committed fix to the 3.3 EE maintenance branch. The issue didn't have to do with an update in the Google Maps code, as initially suspected. The issue had to do with our code, which removes a marker before recreating it again when it's updated. This fix is to persist the same instance in the client, which may be already registered with various event listeners.

                People

                • Assignee:
                  Arturo Zambrano
                  Reporter:
                  Judy Guglielmin
                • Votes:
                  1 Vote for this issue
                  Watchers:
                  4 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: