geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Forrest Xia (Resolved) (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (GERONIMO-5789) OWB always loads all app classes, even if its not a jcdi app.
Date Tue, 10 Jan 2012 08:50:38 GMT

     [ https://issues.apache.org/jira/browse/GERONIMO-5789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Forrest Xia resolved GERONIMO-5789.
-----------------------------------

    Resolution: Fixed

Set status to fixed since some work already done for this issue. 

Feel free to reopen it if you think it's not fixed yet.
                
> OWB always loads all app classes, even if its not a jcdi app.
> -------------------------------------------------------------
>
>                 Key: GERONIMO-5789
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-5789
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: OpenWebBeans
>    Affects Versions: 3.0
>            Reporter: David Jencks
>            Assignee: David Jencks
>             Fix For: 3.0
>
>
> OWB is very tightly integrated into geronimo and openejb so we don't really have the
option to completely turn off OWB.  On app startup OWB currently always scans the entire app
and loads every class (and generally creates metadata for all of them).  For non-jcdi apps
that are marked by not having any beans.xml files, we can just skip scanning classes, so OWB
wont have significant startup overhead.

--
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