Anita44 / gmaps4jsf

Automatically exported from code.google.com/p/gmaps4jsf
0 stars 0 forks source link

Map shows wrong values. Circle/marker not displaying what its supposed to display #201

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
Created a wizard page (JSF), based on a conversation scoped bean.

1. Add a JSF <h:selectOneMenu that holds a few values.
2. Add a JSF <m:map with one marker and with one circle overlay with an 
included <m:htmlInformationWindow tag.
2. Add a JSF <h:commandButton that triggers an ActionEvent to step through the 
wizard.

What is the expected output? What do you see instead?
1. Expected output: When you first load the page... A postconstruct annotation 
triggers a default lat/long for the <m:map, circle, marker lat/long values. 
When located in step 1, the map displays the correct values. When you step to 
the 2nd step its supposed to recalculate the values in the ActionEvent based on 
the h:selectOneMenu value.
2. Seen instead: Marker returned is not located in the correct place,
need to step through the wizard or better to refresh the page in order to get 
the correct display.

What version of the product are you using? On what operating system?
gmaps4jsf 3.0.0,  JSF 2.1    Ubuntu 12.04

Please provide any additional information below.
On step 1 you choose the location and continue with the button that triggers 
the ActionEvent. So on submit (step 1) values are processed based on the 
selection and new long/lat values are calculated. But the new values are not 
displayed correctly on the map. Circle overlay shows something else and marker 
some other position (one step behind). I need to manually refresh the screen to 
get it correct. Even so when i continue through the wizard it shows different 
values on each step.
NOTE that if i display the map (panelgroup rendered) only on step 2 it works 
correct. 

Something to do with the conversation scope? Refreshing the UI gmap? Dont know, 
maybe i'm doing something wrong also...

Thanks

Original issue reported on code.google.com by forza...@gmail.com on 9 Sep 2013 at 8:39