[jax-rs-spec users] [jsr339-experts] Re: Re: Re: Remove @ManagedAsync Re: Re: Re: Latest async API changes

From: Bill Burke <>
Date: Mon, 24 Sep 2012 13:25:28 -0400

On 9/24/2012 1:16 PM, Sergey Beryozkin wrote:
> Hi
> On 15/08/12 18:02, Marek Potociar wrote:
>> Experts,
>> While I disagree with most of what Bill is objecting to, I have not
>> received any other real support for either side from you. So, since I do
>> not feel strongly about having these features in JAX-RS now, to move out
>> of this deadlock situation I have updated the async API proposal as
>> follows:
>> * removed all properties from @Suspended
>> o the injected AsyncResponse is suspended indefinitely by default
>> which may be changed using its programmatic API
>> * removed ConnectionCallback from JAX-RS API
>> * removed @ManagedAsync from JAX-RS API
>> * added varargs versions of AsyncResponse.register() methods.
>> * updated examples and javadoc accordingly
> At the moment, do you see @Suspended (as a parameter-level annotation)
> redundant ? It does seem to me it is:
> @GET
> public String get(@Suspended AsyncResponse) {}

Redundant, but, similarly we don't need @Context either.

> I mean, the runtime can decide what to do based on the fact that a given
> method parameter type is AsyncResponse ?
> The other question, what about the following style:
> @GET
> @Suspended
> public String get() {}

This looks like @ManagedAsync and I thought we closed the book on that...

Bill Burke
JBoss, a division of Red Hat