[
https://issues.apache.org/jira/browse/CXF-7175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15741432#comment-15741432
]
Martin Kouba commented on CXF-7175:
-----------------------------------
I think that Bean.getBeanClass() javadoc is missing clarification for custom
Bean implementations. The spec is clear that the container should use
Bean.getBeanClass() when determining whether a bean is available for injection
(5.1.4. Inter-module injection) and whether it's an alternative selected in a
certain bean archive (Declaring selected alternatives for a bean archive). So
it should be ok to use Bus as a bean class.
The original problem was caused by a bug in Weld, where some methods were not
added to a client proxy if Groovy was on the class path - see also
https://issues.jboss.org/browse/WELD-2255 and
https://issues.jboss.org/browse/WELD-2276.
> Wrong class specified for CdiBusBean
> ------------------------------------
>
> Key: CXF-7175
> URL: https://issues.apache.org/jira/browse/CXF-7175
> Project: CXF
> Issue Type: Bug
> Components: Integration
> Reporter: John D. Ament
>
> https://github.com/apache/cxf/blob/3.1.x-fixes/integration/cdi/src/main/java/org/apache/cxf/cdi/CdiBusBean.java#L43
> This specifies the wrong class. Since the Bean created is specifically a
> {{ExtensionManagerBus}} this should return {{ExtensionManagerBus.class}} not
> {{Bus.class}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
