[
https://issues.apache.org/jira/browse/OWB-284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12834492#action_12834492
]
YING WANG commented on OWB-284:
-------------------------------
Gurkan, I will try to combine both, might take me some time. I am not sure
about some behaviors:
1. Considering following 3 specialized beans:
Bean1
@Alternative @Specializes Bean2 extends Bean1
@Specializes Bean3 extends Bean2
If Bean2 is not enabled in bean.xml, should we report an error, or should still
return Bean3?
2. Are we going to support defining Specialized bean in bean.xml? or I could
ignore checkXMLSpecializations? I didn't see definition of specialized bean in
bean.xml in the spec.
thanks.
> OWB could not find default bean if alternative specialized bean is not
> enabled.
> -------------------------------------------------------------------------------
>
> Key: OWB-284
> URL: https://issues.apache.org/jira/browse/OWB-284
> Project: OpenWebBeans
> Issue Type: Bug
> Components: Injection and Lookup
> Affects Versions: M3
> Reporter: YING WANG
> Assignee: Gurkan Erdogdu
> Attachments: owb284testcase.jar
>
>
> I have 2 managed beans:
> @QualifierSpecialized Bus
> @Alternative @Specializes public class SchoolBus extends Bus
> owb works fine when SchoolBus is enabled in bean.xml. However, if SchoolBus
> is not enabled in bean.xml, owb could NOT locate Bus either.
> (test case will be uploaded later).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
