On 01/18/10 04:22 AM, Paul Sandoz wrote:
>
> On Jan 15, 2010, at 7:26 PM, glassfish_at_javadesktop.org wrote:
>
>> This sounds like a good idea. Sun should communicate this
>> information to all other JAX-RS implementations so they can add the
>> same GlassFish specific support. Too bad this behavior wasn't
>> defined by the JAX-RS specification.
>
> IIRC the source of the issue is different app servers have different
> behavior for default error pages. Is default error page support
> required by the servlet specification?
The default error page seems like a container implementation
detail. All that the Servlet spec requires is the following (see SRV
10.9.2: "Error Pages"):
If a servlet generates an error that is not handled by the error
page mechanism as described above, the container must ensure to
send a response with status 500.
Jan
> If not then this requires some clarification from the Servlet
> specfication before anything at the level of JAX-RS can be specified.
>
> Paul.
>
>> Thanks,
>> Ryan
>>
>>
>>> I should mention that by having Jersey's
>>> ServletContainerInitializer
>>> set the new init parameter, no developer involvement
>>> would be required,
>>> that is, the web container's default error page would
>>> be suppressed for any
>>> JAX-RS requests out-of-the-box, which is what Markus
>>> has been asking for.
>>>
>>>
>>> Jan
>> [Message sent by forum member 'rdelaplante' (ryan_at_ijws.com)]
>>
>> http://forums.java.net/jive/thread.jspa?messageID=381247
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>