[
https://issues.apache.org/jira/browse/OWB-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12846849#action_12846849
]
Gurkan Erdogdu commented on OWB-329:
------------------------------------
>>>This is exactly the reason why the spec explicitly defines that Interceptors
>>>and Decorators must be implemented by subclassing and not via proxying.
We do not proxy the decorators and interceptors. Interceptors and decorators
are created directly. Look at JavassistProxyFactory that is reposible for
creating the dependent instance proxies. Currently we create proxy for
dependent beans that has decorator or interceptors. Decorators and interceptors
do not have other decorators or interceptors therefore they are not proxied.
>>>This solution is a huge performance boost, but suffers from mem leaks
>>>because Contextual#destroy() cannot release
>>>AbstractContext#creationalContextMap.
Actually you must not call the destroy method of the beans directly. Destroy
method is called by the Context instance that its instance live.
>>>... but really problematic with all 3rd p
Indeed, you must not call any methods of the Context interfaces. For 3th party
contexts, we wrap them. Therefore its creatioal context map created/destroyed
in correct phases.
> Interceptor instances get created each time the interceptor gets called
> -----------------------------------------------------------------------
>
> Key: OWB-329
> URL: https://issues.apache.org/jira/browse/OWB-329
> Project: OpenWebBeans
> Issue Type: Bug
> Components: Interceptor and Decorators
> Affects Versions: M4
> Reporter: Mark Struberg
> Assignee: Mark Struberg
> Priority: Critical
> Fix For: 1.0.0
>
>
> Interceptors are defined as being @Dependent scoped. Thus, for one
> @ApplicationScoped contextual instance, only one interceptor instance of a
> certain type must exist. But we currently create a new instance for each and
> every method invocation which is intercepted.
> This is not only terribly slow, but also doesn't work as expected from a
> portable perspective.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
