geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Jencks (JIRA)" <j...@apache.org>
Subject [jira] Commented: (GERONIMO-5789) OWB always loads all app classes, even if its not a jcdi app.
Date Thu, 27 Jan 2011 01:19:43 GMT

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

David Jencks commented on GERONIMO-5789:
----------------------------------------

trunk rev 1063942
3.0-M2 rev 1063945

Leaving it open until there's more confirmation this doesn't break stuff

> 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-M2, 3.0
>            Reporter: David Jencks
>            Assignee: David Jencks
>             Fix For: 3.0-M2, 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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message