Re: Review: Initial Fixes for Issue 125

From: Ed Burns <>
Date: Thu, 14 Jul 2005 14:57:36 -0700

>>>>> On Sun, 03 Jul 2005 01:35:46 -0500, Jacob Hookom <> said:

JH> Ed Burns wrote:
JH> I chatted with Carla at J1 on the need for 'user' documentation for
JH> Glassfish. Jan said he had submitted some stuff to her, but I don't
JH> have a clue as to how we can 'automate' testing against Glassfish when
JH> we had targets working in webtier against Tomcat.
>> Jayashri checked it in. Check out jsf-ri/build.xml.
>> I ran into some problems on the mac, but perhaps it works on your
>> platform.
JH> My Coleco Vision A.D.A.M has problems with Maven in relation to its
JH> cassette drive...

That's funny, it worked just fine with the cassette drive on my

JH> A couple things that should be documented with testing on glassfish:

JH> - you must modify the domain's server.policy to allow setting of System
JH> properties

JH> permission java.util.PropertyPermission "*", "write"; (was "read" by
JH> default)

JH> - Classpath resolution is flipped from tomcat, so it seems. The server
JH> scoped legacy jsf jars have preference over the web app jars and
JH> deleting them from the domain/lib fixed methodnotfound exceptions.

Yes, the classloader preferences are a dark art which will not be
discussed here.

JH> - domain1 is hardcoded in the build-tests.xml, possibly alias it in the
JH> for easy modification