[
https://issues.apache.org/jira/browse/OWB-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12846866#action_12846866
]
Gurkan Erdogdu commented on OWB-329:
------------------------------------
For proxying, my understanding is that: If it is proxy, it is generated from
ProxyHandler in JavasisstProxyFactory, otherwise it is created directly by
bean constructor(via new instance). Decorators/Interceptors do not proxied by
any method handler.
In specification(section 6.3), talks about current context of the scope. In our
implementation, each scope gets its own current context (for example: each
session scoped has its own current session context and it bounds to its thread
local) , what is wrong here? If there is an active current context with given
scope, you can not add any other context with the same scope.
For destroying, it is easy to update code for handling custom context
destroying, for example , changing creational context map to WeakHashMap. also
several other solutions can be done.
> 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.
