You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tomee.apache.org by "David Jencks (JIRA)" <ji...@apache.org> on 2010/10/21 22:34:16 UTC
[jira] Created: (OPENEJB-1382) Provide interceptor/thread based
context for OWB rather than classloader based context
Provide interceptor/thread based context for OWB rather than classloader based context
--------------------------------------------------------------------------------------
Key: OPENEJB-1382
URL: https://issues.apache.org/jira/browse/OPENEJB-1382
Project: OpenEJB
Issue Type: Bug
Components: ejb31
Affects Versions: 3.2
Reporter: David Jencks
Assignee: David Jencks
Fix For: 3.2
OWB currently uses a classloader based scheme for the web bean contexts (basically the singletonService's collection of per-module(?) "singleton" components). Although we don't actually know what the intended scope of this goo is, it's unlikely to correspond to a classloader. So we can replace it with something we set on entering and exiting a context using a ThreadContextListener.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (OPENEJB-1382) Provide interceptor/thread based
context for OWB rather than classloader based context
Posted by "David Jencks (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENEJB-1382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923652#action_12923652 ]
David Jencks commented on OPENEJB-1382:
---------------------------------------
rev 1026147.
There's a big hack in CdiBuilder to initialize the singletonservice if its missing. This gets a lot of tests to pass but doesn't seem like a good idea to me.
> Provide interceptor/thread based context for OWB rather than classloader based context
> --------------------------------------------------------------------------------------
>
> Key: OPENEJB-1382
> URL: https://issues.apache.org/jira/browse/OPENEJB-1382
> Project: OpenEJB
> Issue Type: Bug
> Components: ejb31
> Affects Versions: 3.2
> Reporter: David Jencks
> Assignee: David Jencks
> Fix For: 3.2
>
>
> OWB currently uses a classloader based scheme for the web bean contexts (basically the singletonService's collection of per-module(?) "singleton" components). Although we don't actually know what the intended scope of this goo is, it's unlikely to correspond to a classloader. So we can replace it with something we set on entering and exiting a context using a ThreadContextListener.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.