users@jersey.java.net

[Jersey] Re: Deploying Jersey resources into a Servlet 3.0 API aware container fails miserably

From: Róbert Kohányi <kohanyi.robert_at_gmail.com>
Date: Thu, 13 Oct 2011 11:15:53 +0200

OK. I've found out what I was doing wrong. I've updated my post at SO with
an answer. (Basically I tried reaching
`http://localhost:8080/foo/bar`instead of `
http://localhost:8080/<my war name>/foo/bar`. Be this an example for the
future generation. :D)

Regards,
Kohányi Róbert

On Thu, Oct 13, 2011 at 10:40 AM, Róbert Kohányi
<kohanyi.robert_at_gmail.com>wrote:

> Hi!
>
> I've posted a question on SO (http://stackoverflow.com/q/7750855/433835)
> regarding some strange behavior using Servlet 3.0 API specific approach to
> deploy JAX-RS resources into Jetty 8.0.x with Jersey. (The question contains
> every additional information with the actual classes, a pom.xml for Maven
> and a log output from jetty.)
>
> If someone was so kind to give it a glance it would be greatly appreciated!
> I just don't know what I'm doing wrong.
>
> Thanks in advance!
>
> Regards,
> Kohányi Róbert
>