[
https://issues.apache.org/jira/browse/OWB-402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12884176#action_12884176
]
Gurkan Erdogdu commented on OWB-402:
------------------------------------
Actually this is the same with other injectable Java EE unmanaged objects. JSF
runtime(MyFaces) is responsible for injecting @Inject using JSR299, for example
JSF instantiates myBean instance.
BeanManager#createAnnotatedType(myBean.class);
BeanManager#createInjectionTarget(annotatedType)
InjectionTarget#inject(myBean instance, creational context);
That is how we inject dependencies for Servlets, Filters etc.
To use MyBean in JSF page, you have to given name via @ManagedBean because
JSR299 has no information about them.
> 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.
