I feel your pain. Somewhere between Marc Hadley and Paul Sandoz leaving
this project, both the JAX-RS and Jersey 2.0 communities have become
quite dysfunctional. About the only response you'll get on this list is
"No. We're not dead!" and even then it'll only show up a few days after
your post. Contrast this to projects like HK2 where I get an answer
within 15 minutes of posting a question, and bugs that I report get
fixed within the next release cycle. There are many other projects that
are amazing this way. Jersey 1.0 used to be such a project.
And we're not the only ones who noticed that something is broken. See
https://groups.google.com/d/msg/dropwizard-user/w7jqlCqU-00/7EA228e5Ps4J
There seems to be a strong consensus that Jersey 2.0 is missing critical
features from 1.0 and yet they are not receiving top priority. I'd love
to see some genuine action to close these gaps. I tried digging into the
code myself, in the hopes of producing pull requests, but some of these
problems are design-level which make them difficult to fix as an outsider.
Gili
On 06/12/2013 10:29 AM, Rodrigo Lopes wrote:
>
> Has Oracle just abandoned this project?
>
>
> I was checking open tickets for JAX projects; 63 tickets unassigned
> (100%).
>
> https://java.net/jira/browse/JAX_RS_SPEC/fixforversion/14716
>
> "So what..."
>
> It is in fact worse: You can find junks and SPAMs within the tickets:
>
> https://java.net/jira/browse/JAX_RS_SPEC-276
>
> Has Oracle no more interesting in this spec?
>
> Best regards,
>
>
> Rodrigo di Lorenzo Lopes
>