@Alternative broken if multiple implementations are in the classpath
--------------------------------------------------------------------
Key: WELD-905
URL: https://issues.jboss.org/browse/WELD-905
Project: Weld
Issue Type: Bug
Components: Resolution (Typesafe and by Name)
Affects Versions: 1.1.1.Final
Reporter: Gerhard Petracek
Priority: Critical
example (broken):
bean-archive #1:
- BeanA
- BeanA1 (@Alternative)
- beans.xml (activates BeanA1 as alternative)
bean-archive #2:
- BeanA2 (@Typed())
- beans.xml (empty)
BeanA1 doesn't get used (without an error or a warning BeanA is used instead -
even though BeanA1 is activated as alternative in the same bean-archive)
example (working):
bean-archive #1:
- BeanA
- BeanA1 (@Alternative)
- beans.xml (activates BeanA1 as alternative)
jar #2 (no bean-archive):
- BeanA2 (@Typed())
BeanA1 gets activated as alternative (as expected) because jar #2 isn't a
bean-archive (that's the difference compared to the broken example).
that prevents >e.g.< portable extensions from providing extension-points to
work around the broken @Alternative spec. section.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
weld-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/weld-issues
