Paul,
actually I do not understand your beginning "No." -- you just repeated
the same idea that I posted: That it is not Jersey's fault but
GlassFish's! Maybe you misunderstood my posting? 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/>
Regards
Markus
From: Paul.Sandoz_at_Sun.COM [mailto:Paul.Sandoz_at_Sun.COM]
Sent: Donnerstag, 14. Januar 2010 12:52
To: users_at_glassfish.dev.java.net
Subject: Re: JAX-RS error code 500 = GlassFish HTML error page
On Jan 14, 2010, at 8:16 AM, Markus Karg wrote:
I'd like to mention that GlassFish should be aware of the difference
between a JAX-RS response and a servlet response. Why? Because JAX-RS is
an API for writing *services*
No. JAX-RS can be used for writing RESTful Web applications serving
HTML, XML and JSON depending on what the client accepts (e.g. see the
RESTful admin support, or stuff what is being done in Apache Camel).
There is stuff in Jersey to enable just that (the MVC stuff).
I do not think this issue is specific to just JAX-RS/Jersey but to any
Servlet-based Web application. Invariably when one wants to deploy a Web
application in production then the default error pages will likely be
changed to something particular to the Web application. (And i do see
value in GF providing support for just that with customizable themes.)
Paul.