[jira] Commented: (OWB-538) introduce proprietary configuration option to ignore not explicitly marked (via annotation or registered by extension) Dependent beans

["David Jencks (JIRA)" <ji...@apache.org>]

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

David Jencks commented on OWB-538:
----------------------------------

I think the real problem here is that owb currently loads every application class and creates metadata for almost all of them.  I think there may be a way to avoid this while not introducing any proprietary limitations or configuration.

We can easily find all the classes that are explicitly annotated or explicitly injected.  I think there's little doubt we should find these classes, load them, and create metadata for them on app startup.  However there are some dynamic ways of asking for web beans that cannot be detected through annotation scanning.  Can we arrange to create the metadata for these beans lazily when one of the dynamic methods is called?

BTW I don't recall any errors from the current "load everything" strategy.... what kinds of errors are you thinking of?

> introduce proprietary configuration option to ignore not explicitly marked (via annotation or registered by extension) Dependent beans
> --------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: OWB-538
>                 URL: https://issues.apache.org/jira/browse/OWB-538
>             Project: OpenWebBeans
>          Issue Type: New Feature
>          Components: Injection and Lookup
>    Affects Versions: 1.0.0
>            Reporter: Mark Struberg
>            Assignee: Mark Struberg
>             Fix For: 1.1.0
>
>
> The JSR-299 spec defines that not annotated beans must get picked up as being @Dependent by default.
> But this 
> a) introduces many errors in projects
> b) unnecessarily fills up our managed beans list 
> c) causes lots of unnecessary work while scanning the classes.
> Thus I'd like to propose the introduction of a non spec compliant flag 'useExplicitDependentScoped' which is false by default

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira