[jira] Resolved: (APA-14) GoogleMaps Event Demo not working correctly on Desktop

["Woonsan Ko (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/APA-14?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Woonsan Ko resolved APA-14.
---------------------------

    Resolution: Fixed

The problem seems to be caused by a subtle timing issue when the browser refreshes the javascript functions.
That is, google maps api could invoke the old javascript callback function before it is refreshed during rendering.
By using global javascript variable, it seems working now.

> GoogleMaps Event Demo not working correctly on Desktop
> ------------------------------------------------------
>
>                 Key: APA-14
>                 URL: https://issues.apache.org/jira/browse/APA-14
>             Project: Portals Apps
>          Issue Type: Bug
>    Affects Versions: apa-demo-1.0
>            Reporter: Woonsan Ko
>            Assignee: Woonsan Ko
>             Fix For: apa-demo-1.0
>
>
> The followings are copied from JS2-1012, which is turned out to be GoogleMaps problem.
> ---------------------------
> The Event Demo demonstrates the Portlet 2.0 Event features. It works on /portal, but doesn't work on /desktop. The event is received but doesn't get updated in doView until subsequent doView cycles. I think we need to build in an event cycle into the /desktop. To reproduce:
> 1. navigate to http://localhost:8080/jetspeed/desktop/Public/map.psml, you should see the default Map, San Francisco
> 2. enter "Detroit" (or any address will do)
> 3. the page still displays SF
> 4. refresh, or maximize, the correct Detroit map now displays
> --------------------------
> Turns out events are working fine. Render parameters set from an event are not being picked up on the next render request. However, subsequent render requests (next render request + 1) do pick up the render parameters
>  response.setRenderParameter("address", payload.getAddress());
> [ Show » ]
> David Sean Taylor added a comment - 16/May/09 10:49 AM Turns out events are working fine. Render parameters set from an event are not being picked up on the next render request. However, subsequent render requests (next render request + 1) do pick up the render parameters  response.setRenderParameter("address", payload.getAddress());

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.