I'm sure that rich:gmap is not implemented in 4.0.0 M5 and it's not going to be implemented until 4.0.0 Final is released. The problem is that there are a lot of components like rich:gmap, rich:page, a4j:include etc. which are not implemented in 4.0.0 because RF team does not have enough to time take care of all the components from 3.3.3. Right now they need to implement all the essential components and make an enough stable release. After 4.0.0 is released all the components which are the part of 3.3.3 but not represented in 4.0.0 will be put into the roadmap. I suggest you to monitor the situation and ask a question about a schedule of rich:gmap again after 4.0.0 is released.
1 of 1 people found this helpful
Minor clarification.. some components (and GMap one of them) not included not just because of timing issue but because it's required review and redesign from functional point of view. In 3.3.x that component just draw the map and all the other functionality was accessible only using client side component object. Now we want to provide new usefull tags and/or attributes in order to make work with the component more convinient. So it's not just pure migration.
Thanks for the help guys.
I ll keep an eye for updates and I cant wait for the final release, thnks!