On 4/20/12 11:38 AM, Santiago Pericas-Geertsen wrote:
>
> On Apr 20, 2012, at 11:28 AM, Bill Burke wrote:
>
>>
>>
>> On 4/20/12 11:18 AM, Santiago Pericas-Geertsen wrote:
>>>
>>> On Apr 19, 2012, at 8:46 AM, Bill Burke wrote:
>>>
>>>>>>
>>>>>> Why not both? As you say, (1) is more flexible but (2) is quite
>>>>>> convenient.
>>>>>>
>>>>>
>>>>> I don't understand how the sub-resource injection can work at all.
>>>>> Lets take an example where a root resource is a singleton.
>>>>>
>>>>> This root resource can return sub-resource instances. Such instances can
>>>>> be created at a per-request basis or may've been pre-allocated and are
>>>>> singletons too. Only the root resource knows the rules.
>>>>>
>>>>> How can the runtime make sure that the injection into sub-resources is
>>>>> thread-safe ?
>>>>>
>>>>
>>>> Another thing, if the sub-resource is an EJB or CDI bean, won't injection happen anyways?
>>>
>>> Yes, but not for @Context stuff, right?
>>>
>>
>> Why wouldn't/shouldn't it?
>
> Because the EJB or CDI container don't understand the meaning of @Context?
>
Errr...they are supposed to. Hence section 6.2 of the specification?
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com