[
https://issues.apache.org/jira/browse/OWB-655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13234939#comment-13234939
]
Mark Struberg commented on OWB-655:
-----------------------------------
I also don't think the abstract base type should be a problem. What counts is
that the AppJpaDAO class is a valid type.
I do think that in this very case we could lookup the EJB if we don't find a
CDI Bean<PlcBaseDAO>. But in general the spec is imo not 100% clear what should
happen with such 'mixed' scenarios: what happens if we have an
@ApplicationScoped class OtherAppJpaDAO extends PlcBaseJpaDAO {} ?
There are no @Alternative, @Specializes etc rules for mixed EJB/CDI cases
defined yet imo.
> CDI doesn´t inject stateless EJB by abstract class.
> ---------------------------------------------------
>
> Key: OWB-655
> URL: https://issues.apache.org/jira/browse/OWB-655
> Project: OpenWebBeans
> Issue Type: Bug
> Components: Enterprise Web Beans
> Affects Versions: 1.1.3
> Reporter: Rogerio Baldini
> Assignee: Gurkan Erdogdu
>
> I have these classes:
> public abstract class PlcBaseDAO {}
> public abstract class PlcBaseJpaDAO extends PlcBaseDAO {}
> @Stateless
> public class AppJpaDAO extends PlcBaseJpaDAO {}
> And this injection doesn´t work.
> @Named
> public class AppCDI {
> @Inject
> private PlcBaseDAO baseDao;
> }
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
