[
https://issues.apache.org/jira/browse/OWB-402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12884292#action_12884292
]
Mark Struberg commented on OWB-402:
-----------------------------------
Since this is still more controversal than I thought, I'll reopen the issue.
regarding the EE6 @ManagedBean. This got introduced in the very last moment by
Roberto Chinnici, and I have _absolutely_ no clue why and what for. There was
also almost no discussion on the EE EG. Jürgen Höller pointed me to this spec
part back in March and we had a few good laughs while reading the spec and
easily finding just a bunch of obvious inconsistencies. So I for myself will
simply ignore this annotation because imo it is just a placeholder to get
something in to the maintenance release of JSR-316 (It's forbidden to introduce
new features in a JSR MR, but 'fixing' is allowed).
> OpenWebBeansJsfPlugin does not recognize @ManagedBean
> -----------------------------------------------------
>
> Key: OWB-402
> URL: https://issues.apache.org/jira/browse/OWB-402
> Project: OpenWebBeans
> Issue Type: Bug
> Components: Java EE Integration
> Affects Versions: M4
> Reporter: Joe Bergmark
> Assignee: Joe Bergmark
> Priority: Minor
> Fix For: 1.0.0-CR2
>
>
> OpenWebBeansJsfPlugin does not recognize @ManagedBean as a managed bean.
> Right now it only throws and Exception when it is passed a UIComponent (a JSF
> component).
> In the longer term, it seems like it should both
> 1) Look for the @ManagedBean annotation on the class
> 2) Look for other beans defined in the faces-config.xml (possibly harder)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
