You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@geronimo.apache.org by "David Jencks (JIRA)" <ji...@apache.org> on 2011/01/27 02:09:44 UTC

[jira] Created: (GERONIMO-5789) OWB always loads all app classes, even if its not a jcdi app.

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.

[jira] Commented: (GERONIMO-5789) OWB always loads all app classes, even if its not a jcdi app.

Posted by "David Jencks (JIRA)" <ji...@apache.org>.

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

[jira] [Resolved] (GERONIMO-5789) OWB always loads all app classes, even if its not a jcdi app.

Posted by "Forrest Xia (Resolved) (JIRA)" <ji...@apache.org>.

     [ 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