[
https://issues.apache.org/jira/browse/OWB-538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13000496#comment-13000496
]
Mark Struberg commented on OWB-538:
-----------------------------------
I was not talking about OWB errors, but application errors. E.g. if someone
accidently uses a java.faces.beans.SessionScoped instead of the CDI
@SessionScoped (with auto import in IDEs this happens pretty often), then the
bean is effectively @Dependent and thus breaking the application logic in most
cases.
Also you will get an AmbiguousResolutionExceptions if you create a
ProducerMethod for a POJO because there are 2 beans then: the
ProducerMethodBean and the auto-pickup @Dependent Bean. Pretty annoying it is...
> 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
