[
https://issues.apache.org/jira/browse/OWB-402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12884279#action_12884279
]
Joe Bergmark commented on OWB-402:
----------------------------------
I'm not talking about JSR-314, I'm referring to the high level EE6 spec itself,
and is detailed specifically in EE.5.20. It references a table of all of the
components that need to support @Inject, and those component include
@ManagedBean, all JSF beans, Servlets, Filters, etc etc etc. While MyFaces as
a stand alone JSF container doesn't need a reference to @Inject, when it is
part of a full EE6 container there does need to be support for @Inject inside
of JSF Managed Beans.
Gurkan, for some reason I thought the fact that our plugin didn't return
"false" for isManagedBean, meant no injection would occur. Perhaps the code on
our side is trying to protect from double injection by not calling inject for
something that will later be injected by a OWB (because it is a managed bean)
I'll look into this further. Thanks for the pointer.
> 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.
