Closed GoogleCodeExporter closed 9 years ago
OK, with some google searching I think I have found out what is going on.
This turns out to be a gmaps api problem, not an issue with gmaps4jsf. However
it would be nice if gmaps4jsf could implement a work-around since it seems to
be something of a persistent problem.
I'll put the answer I have here for those who have run into this:
To work around this problem, enclose the facelets code in an <f:view
contentType="text/html"> tag. By default Faces will render the facelet as an
XML document, and this otherwise unnecessary tag will cause it to render an
HTML document.
The difference is that for the browser, an HTML document has a Document.write()
method and the XML document does not. The gmap api library depends on that
method call. So if you are including the gmaps API in your pages, they have to
be HTML and not XHTML documents.
I am not sure what workaround gmaps4jsf could provide, but it would have to be
in some form of wrapper script in the header that would intercept that method
invocation and do something with it. It would be better fixed in gmaps API.
Original comment by OmegaObj...@gmail.com
on 4 Oct 2010 at 3:10
Original comment by Hazem.sa...@gmail.com
on 29 Oct 2010 at 1:04
Original issue reported on code.google.com by
OmegaObj...@gmail.com
on 3 Oct 2010 at 5:17