You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openwebbeans.apache.org by Romain Manni-Bucau <rm...@gmail.com> on 2014/10/12 15:45:00 UTC
ApplicationScopedBeanInterceptorHandler broken?
Hi guys,
when using ApplicationScopedBeanInterceptorHandler we can't pass TCKs
cause it cached instances so then is you use AlterableContext you keep
the cached instance.
By default we use just NormalScopedBeanInterceptorHandler and all
works fine. To solve this issue we should keep tracking proxies and
reset them when destroy is called.
I don't think it does worth it but it was mainly to share it since
ApplicationScopedBeanInterceptorHandler is still nice to use :).
Romain Manni-Bucau
@rmannibucau
http://www.tomitribe.com
http://rmannibucau.wordpress.com
https://github.com/rmannibucau
Re: ApplicationScopedBeanInterceptorHandler broken?
Posted by Romain Manni-Bucau <rm...@gmail.com>.
same here but saw it in tomee, was mainly to share it ;)
Romain Manni-Bucau
@rmannibucau
http://www.tomitribe.com
http://rmannibucau.wordpress.com
https://github.com/rmannibucau
2014-10-12 19:17 GMT+02:00 Mark Struberg <st...@yahoo.de>:
> Hi Romain!
>
> Yes for the TCK we should probably switch to the non-caching proxy (NormalScopedBeanInterceptorHandler).
>
> In real world applications I have never seen the need to delete ApplicationScoped services though.
>
> Every user can easily overwrite the proxy to use via it's own openwebbeans.properties provided in his own jar. There is even the possibility to provide own proxy handler with their own caching logic per scope.
> Gerhard did such things for the MyFaces CODI scopes back then and it improved the performance of our app notably.
>
> LieGrue,
> strub
>
>
>
>
>> On Sunday, 12 October 2014, 15:45, Romain Manni-Bucau <rm...@gmail.com> wrote:
>> > Hi guys,
>>
>> when using ApplicationScopedBeanInterceptorHandler we can't pass TCKs
>> cause it cached instances so then is you use AlterableContext you keep
>> the cached instance.
>>
>> By default we use just NormalScopedBeanInterceptorHandler and all
>> works fine. To solve this issue we should keep tracking proxies and
>> reset them when destroy is called.
>>
>> I don't think it does worth it but it was mainly to share it since
>> ApplicationScopedBeanInterceptorHandler is still nice to use :).
>>
>>
>> Romain Manni-Bucau
>> @rmannibucau
>> http://www.tomitribe.com
>> http://rmannibucau.wordpress.com
>> https://github.com/rmannibucau
>>
Re: ApplicationScopedBeanInterceptorHandler broken?
Posted by Mark Struberg <st...@yahoo.de>.
Hi Romain!
Yes for the TCK we should probably switch to the non-caching proxy (NormalScopedBeanInterceptorHandler).
In real world applications I have never seen the need to delete ApplicationScoped services though.
Every user can easily overwrite the proxy to use via it's own openwebbeans.properties provided in his own jar. There is even the possibility to provide own proxy handler with their own caching logic per scope.
Gerhard did such things for the MyFaces CODI scopes back then and it improved the performance of our app notably.
LieGrue,
strub
> On Sunday, 12 October 2014, 15:45, Romain Manni-Bucau <rm...@gmail.com> wrote:
> > Hi guys,
>
> when using ApplicationScopedBeanInterceptorHandler we can't pass TCKs
> cause it cached instances so then is you use AlterableContext you keep
> the cached instance.
>
> By default we use just NormalScopedBeanInterceptorHandler and all
> works fine. To solve this issue we should keep tracking proxies and
> reset them when destroy is called.
>
> I don't think it does worth it but it was mainly to share it since
> ApplicationScopedBeanInterceptorHandler is still nice to use :).
>
>
> Romain Manni-Bucau
> @rmannibucau
> http://www.tomitribe.com
> http://rmannibucau.wordpress.com
> https://github.com/rmannibucau
>