On Jan 18, 2010, at 8:02 AM, Markus Karg wrote:
> Once more I want to mention that from the view of architecture and
> the WORA principle, this is not very smart: It enforces all JAX-RS
> implementations to learn about the particular GlassFish product. A
> good solution would be that a JAX-RS implementation doesn't have to
> know about GlassFish, but that GlassFish learns that a JAX-RS
> resource must not be fitted with an error page.
Either way it is gonna require some standardization in JAX-RS may
maybe servlet to make this portable.
Paul.
>
>> -----Original Message-----
>> From: glassfish_at_javadesktop.org [mailto:glassfish_at_javadesktop.org]
>> Sent: Freitag, 15. Januar 2010 20:26
>> To: users_at_glassfish.dev.java.net
>> Subject: Re: JAX-RS error code 500 = GlassFish HTML error page
>>
>> 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.
>>
>>
>> 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
>