[
https://issues.apache.org/jira/browse/OWB-402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg resolved OWB-402.
-------------------------------
Resolution: Not A Problem
Hi Joe!
The decission to _not_ pickup @ManagedBean annotated classes automatically as
beans is because of the ownership problems between OWB and JSF. So we knowingly
ignore this annotation currently.
Plus, I'm pretty sure that this annotation will die sooner or later...
Just as a short overview: there are currently 4 IOC systems around in EE6
(which is _really_ stupid in the end, but it's historically grown)
1.) JSR-330
2.) JSR-299
3.) JSR-314 @ManagedBean from JSF
4.) JSR-316 @MangedBean from the EE6 umbrella spec (yesssss, those guys
introduced some this crap in the last moment before they finished the spec)
All of them define different rules and 'masters' (aka who is actually doing the
injection).
So until now, I was pretty fine with doing our stuff and just ignoring all the
other things ;)
> 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.
