geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Forrest Xia (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GERONIMO-6005) Unclear how big a cdi context is for an ear
Date Wed, 28 Dec 2011 08:35:30 GMT

    [ https://issues.apache.org/jira/browse/GERONIMO-6005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13176522#comment-13176522
] 

Forrest Xia commented on GERONIMO-6005:
---------------------------------------

Is it still a valid improvement for 3.0-beta and trunk code stream? Please help review and
update this jira's status. thanks!
                
> Unclear how big a cdi context is for an ear
> -------------------------------------------
>
>                 Key: GERONIMO-6005
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-6005
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: general
>    Affects Versions: 3.0
>            Reporter: David Jencks
>            Assignee: David Jencks
>             Fix For: 3.0
>
>         Attachments: share-owb-context.diff
>
>
> The cdi spec and pete muir are a bit unclear on how many web beans contexts there are
for an ear.  At the moment the behavior is ridiculous: the ejb module sets one up using the
openejb lifecycle (good) and then the web module sets one up for the same classes using the
web lifecycle (bad).  At least until we understand what is supposed to happen and have separate
bundles for each module the best solution (IMO) is to have a single web beans context for
the entire ear, set up by openejb. This involves a slight change in the existing sharing logic.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message