Hi Markus,
I think default error page support should be disabled by default for
*any* deployed servlet and there is no need to distinguish between JAX-
RS and Servlet deployments in this case.
On Jan 14, 2010, at 1:34 PM, Markus Karg wrote:
> Paul,
>
> actually I do not understand your beginning "No." -- you just
> repeated the same idea that I posted:
Not quite. I do not agree with the following:
GlassFish should be aware of the difference between a JAX-RS
response and a servlet response
you can write a RESTful Web *service* using Servlet (or using a
framework layering on top of Servlet) and you can write a RESTful Web
*application* using JAX-RS (which layers on top of servlet for GF
deployments).
For some *service* is often used to categorize an API that produces/
consumes say JSON/XML and *application* is often used to categorize a
browser-based application. I personally do not see the need for such a
distinction from a REST perspective.
> That it is not Jersey's fault but GlassFish's! Maybe you
> misunderstood my posting?
No. I agree this is a GlassFish issue.
> I explicitly wanted to say that GlassFish shall abstain from mixing
> in any ideas into JAX-RS's way, being error pages or anything else.
> Just what you also wrote in your second paragraph. <confused/>
>
I stated:
I do not think this issue is specific to just JAX-RS/Jersey but to
any servlet-based Web application.
Paul.