On 09/16/2011 12:30 PM, Carlo de Wolf wrote:
On 09/16/2011 05:09 PM, David M. Lloyd wrote:
> The client cannot know whether it was designated as such, since the
> designation may be on the DD (also 4.5.1) which may not be visible to
> the client. So whatever means we have to determine this fact we should
> utilize. If there is a case where a non-async method legitimately could
> return Future, then we can skip this trick. Also, see below...
The way the spec is now a method must be designated as asynchronous
either by @Asynchronous or via the DD.
It does not allow the return type to be used for designation. So there
is your legitimate case.
Well, the spec also doesn't allow the client to decide for itself, but
we're clearly taking at least that liberty already.
--
- DML