Are you thinking of something like an @Pooled annotation? I think this could be very useful indeed for certain use cases. In fact I had suggested this within the context of JMS 2.
> On Feb 24, 2016, at 8:27 AM, arjan tijms <arjan.tijms_at_gmail.com> wrote:g e
>
> p.s.
>
> A small feature request, but what about the ability for Interceptors to intercept before bean resolution has taken place? E.g. in CDI before Context#get is being called.
>
> This could be done without API changes by using a negative value in @Priority for this.
>
> The use case is implementing something like the EJB implicit pooling feature of @Stateless beans. This is very hard to do with interceptors that only get called after a bean instance is created.
>
> Kind regards,
> Arjan Tijms
>
>
>
>> On Wed, Feb 24, 2016 at 10:42 AM, arjan tijms <arjan.tijms_at_gmail.com> wrote:
>> Hi,
>>
>>> On Wed, Feb 24, 2016 at 12:54 AM, Linda DeMichiel <linda.demichiel_at_oracle.com> wrote:
>>> My expectation is that this
>>> would be an "errata MR" (Rev A) as I am not planning any API changes.
>>
>> Should the MR result in any need for behaviour changes, is there any plan or roadmap to apply these changes to GlassFish 5?
>>
>> Kind regards,
>> Arjan Tijms
>>
>>
>