[
https://issues.apache.org/jira/browse/OWB-402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12884181#action_12884181
]
Mark Struberg commented on OWB-402:
-----------------------------------
Joe, the JSR-314 final spec is from 2009-06-25 and doesn't mention JSR-330 nor
@Inject a single time. This has been finalized at a time where the JSR-330 EG
hasn't even formed. Also a grep through MyFaces confirmes this by not finding a
single javax.inject.Inject import.
Consider javax.faces.bean.ManagedBean a dinosaur which will went down the way
of history sooner or later. I personally would recomment NOT using it!
There will be a flag in MyFaces to completely disable their internal
ManagedBean stuff some day. And from this day on we imo might pickup
@ManagedBeans which have no CDI annotation (because then there is no double
handling anymore). I'm not sure if it would be wise to pick them up yet.
Anyway you can use normal CDI beans with MyFaces just fine.
> 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.
