Modifying default-web.xml will affect all the applications.
If you only want to modifying this for a particular web-application,
then one can change web.xml in the given war file.
Shing Wai Chan
On 3/1/11 2:06 PM, Tom Mueller wrote:
> This is a result of issue 15560:
> http://java.net/jira/browse/GLASSFISH-15560
>
> The 3.0.1 included every single GlassFish class in the classpath that
> was used to compile the Java generated from JSPs. This was incorrect
> as an application should only have access to the standard interfaces,
> not the internal implementation classes of the container. An
> application that depends on a com.sun.* class is not going to be
> portable.
>
> In 3.1, by default, only the standard packages are included.
>
> The list of JAR files is in the default-web.xml file in the config
> directory of your domain. You can edit this to include the JAR file
> that contains the com.sun.jersey.api.client package. See the
> "system-jar-includes" variable.
>
> Tom
>
>
>
> On 3/1/2011 3:47 PM, vince kraemer wrote:
>> Hi all,
>>
>> I have a web app that deploys and executes on GF 3.0.1 but it fails
>> to run when I run it (after it deploys successfully) it onto GF 3.1...
>>
>> The error that I see in the server log is this...
>>
>> PWC6199: Generated servlet error:
>> string:///index_jsp.java:60: cannot access
>> com.sun.jersey.api.client.UniformInterfaceException
>> class file for com.sun.jersey.api.client.UniformInterfaceException
>> not found
>>
>> It looks like com.sun.jersey.api.client.* was 'part' of the runtime
>> environment of GF 3.0.1 and is not part of the rte in 3.1.
>>
>> Is this a bug in 3.0.1 or a bug 3.1?
>>
>> If it was a bug in 3.0.1 (which was corrected in 3.1), does anybody
>> know the JIRA id for the issue?
>>
>> Thanks,
>> vbk
>>