Don't forget to make this work for the Filter way of configuring JAX-RS. When I use Jersey's servlet configuration, it doesn't handle any requests. Either that, or JSF stops working -- I forget. I had to use the Filter configuration instead.
In a Java EE 6 environment, how will JAX-RS/Jersey be configured? It will not be in my web.xml, but maybe GlassFish provides a default web-fragment.xml or default web.xml that contains the servlet or filter way of configuring Jersey? What if it uses the servlet way of doing it, then JSF web apps stop working? I didn't look deeper into the problem once I found that the filter configuration worked for me.
Thanks,
Ryan
> 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=381250