By the way, as far as the process is concerned, should we have what are
seen by some people as critical api/spec issues discussed at this list
first ?
I can see/understand why going ahead with the actual fix and then asking
for the review works, especially when the time is limited and such, but
I'm not sure this is the way it should work; to be honest I do not see
much scope for an api like this be removed now that it's been added - we
are now working with the implicit presumption this is an absolutely
essential fix.
Sergey
On 24/08/12 17:34, Marek Potociar wrote:
> Experts,
>
> as a resolution of a critical issue
> http://java.net/jira/browse/JAX_RS_SPEC-72 a new ResourceContext API has
> been introduced. Please see the change here:
> http://java.net/projects/jax-rs-spec/sources/git/revision/d6a07ec69f2f0bae5c93f641247a0a493434f52b
>
> Your review feedback & comments are welcome.
>
> Many thanks,
> Marek