Hi Jacob,
Steps to run the tests with Glass Fish are already documented here.
https://javaserverfaces.dev.java.net/faq.html
I didn't make the domain configurable for simplicity. But if you think
its useful to do that, we can certainly change it.
Thanks
-Jayashri
Jacob Hookom wrote:
> Oops, the server.policy should be changed to "read,write"
>
> Jacob Hookom wrote:
>
>> 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.
>>>
>>>
>> My Coleco Vision A.D.A.M has problems with Maven in relation to its
>> cassette drive...
>>
>> A couple things that should be documented with testing on glassfish:
>>
>> - you must modify the domain's server.policy to allow setting of
>> System properties
>>
>> permission java.util.PropertyPermission "*", "write"; (was "read" by
>> default)
>>
>> - Classpath resolution is flipped from tomcat, so it seems. The
>> server scoped legacy jsf jars have preference over the web app jars
>> and deleting them from the domain/lib fixed methodnotfound exceptions.
>>
>> - domain1 is hardcoded in the build-tests.xml, possibly alias it in
>> the build.properties.glassfish for easy modification
>>
>> ... possibly more to come.
>>
>> Thanks,
>> Jacob
>>
>>>
>>>
>>> Ed
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe_at_javaserverfaces.dev.java.net
>>> For additional commands, e-mail: dev-help_at_javaserverfaces.dev.java.net
>>>
>>>
>>>
>>>
>>
>>
>
>