Closed GoogleCodeExporter closed 9 years ago
I need to modify this slightly. I do not believe that Glassfish was the
problem that
started this issue -- at least not on my site. At this point I am continuing
development with Firefox as my test browser and I have encountered no problems.
(I
also test with Safari and IE and also no problems).
It is Chrome browser with which this is the problem. My particular Chrome
browser
installation can run all the off-site examples run from the off-site servers;
just
not any example so far that is loaded on my local system. I have not had a
chance to
fully diagnose this problem, but it could be some problem with a plug-in I have.
As a side note, I DID run into some problems when using the 1.1.3beta snapshot
under
Glassfish. When I first imported the library I carelessly included all the jar
files
in the snapshot. This includes files such as jsf-facelets.jar and
jsf-impl.jar, etc.
These seem to have some kind of problem with Glassfish where object rendering
screws
up without a diagnostic message. For example the selectBooleanCheckbox tag no
longer
works. To use the snapshot with GlassFish successfully, include only the
following
jars:
gmasp4jsf-core-1.1.3-SNAPSHOT.jar
common-annotations.jar
commons-beanutils.jar
commons-collections.jar
commons-digester.jar
commons-logging.jar
Some of those may already be in your classpath from another library, but this
recipe
works for me.
Original comment by Alan.Deikman
on 14 Nov 2009 at 5:03
Hey we have used Gmaps4JSF for some time now inside of Glassfish 2.1. It works
fine
for us in all browsers. I would look at Firebug for any JS errors...
Original comment by brent.fr...@gmail.com
on 18 Dec 2009 at 12:49
This is a working example on NetBeans and JSF2.0:
http://mashups4jsf.googlecode.com/files/mashups4jsfNetBeansProject-0.0.21.zip
The most important part you should take care is to set the contentType to
text/html,
check this post:
http://www.jroller.com/HazemBlog/entry/uncaught_typeerror_object_a_document
Original comment by Hazem.sa...@gmail.com
on 4 Jan 2010 at 6:48
Original issue reported on code.google.com by
Hazem.sa...@gmail.com
on 7 Nov 2009 at 1:20