[JBoss JIRA] Created: (WELD-905) @Alternative broken if multiple implementations are in the classpath
2:17 p.m.
@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
12:06 a.m.
New subject: [JBoss JIRA] Commented: (WELD-905) @Alternative broken if multiple implementations are in the classpath
[
https://issues.jboss.org/browse/WELD-905?page=com.atlassian.jira.plugin.s...
]
Pete Muir commented on WELD-905:
--------------------------------
Could you attach this as an example, I'm struggling to understand the pseudo
version...
@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
12:28 p.m.
New subject: [JBoss JIRA] Commented: (WELD-905) @Alternative broken if multiple implementations are in the classpath
[
https://issues.jboss.org/browse/WELD-905?page=com.atlassian.jira.plugin.s...
]
Gerhard Petracek commented on WELD-905:
---------------------------------------
2 bean archives. in archive one is an impl. + an alternative (the alternative is activated
in the beans.xml). in the 2nd bda is a class which extends the impl. of the first jar (but
it's annotated with @Typed()) -> due to this 2nd @Typed() impl. the alternative
impl. of the first jar stops working (if you remove the 2nd jar it works again - no
changes in the first jar).
maybe again a glassfish 3.1 issue which might work in glassfish 3.2
@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
2:33 a.m.
New subject: [JBoss JIRA] Commented: (WELD-905) @Alternative broken if multiple implementations are in the classpath
[
https://issues.jboss.org/browse/WELD-905?page=com.atlassian.jira.plugin.s...
]
Stuart Douglas commented on WELD-905:
-------------------------------------
Which jar contains the injection point that you are trying to inject your alternative bean
into?
@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
2:47 a.m.
New subject: [JBoss JIRA] Commented: (WELD-905) @Alternative broken if multiple implementations are in the classpath
[
https://issues.jboss.org/browse/WELD-905?page=com.atlassian.jira.plugin.s...
]
Gerhard Petracek commented on WELD-905:
---------------------------------------
the injection point is in a bean located directly in the web-app -> war-file.
@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
2:49 a.m.
New subject: [JBoss JIRA] Issue Comment Edited: (WELD-905) @Alternative broken if multiple implementations are in the classpath
[
https://issues.jboss.org/browse/WELD-905?page=com.atlassian.jira.plugin.s...
]
Gerhard Petracek edited comment on WELD-905 at 6/16/11 8:47 PM:
----------------------------------------------------------------
the injection point is in a bean which is located directly in the web-app -> war-file.
was (Author: gpetracek):
the injection point is in a bean located directly in the web-app -> war-file.
@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
3 a.m.
New subject: [JBoss JIRA] Commented: (WELD-905) @Alternative broken if multiple implementations are in the classpath
[
https://issues.jboss.org/browse/WELD-905?page=com.atlassian.jira.plugin.s...
]
Stuart Douglas commented on WELD-905:
-------------------------------------
This looks like it may be related to a different GF 3.1 bug that has already been fixed.
If you remove BeanA2 from jar2 and leave the beans.xml in jar2 does it still fail?
@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
1:28 p.m.
New subject: [JBoss JIRA] Commented: (WELD-905) @Alternative broken if multiple implementations are in the classpath
[
https://issues.jboss.org/browse/WELD-905?page=com.atlassian.jira.plugin.s...
]
Gerhard Petracek commented on WELD-905:
---------------------------------------
if i change the constellation it would work. the point is that this constellation
doesn't work but it should.maybe we should test it with jboss as 7.
@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
4:51 p.m.
New subject: [JBoss JIRA] (WELD-905) @Alternative broken if multiple implementations are in the classpath
[
https://issues.jboss.org/browse/WELD-905?page=com.atlassian.jira.plugin.s...
]
Ales Justin commented on WELD-905:
----------------------------------
Do we have some Arquillian test for this?
@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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:41 p.m.
New subject: [JBoss JIRA] (WELD-905) @Alternative broken if multiple implementations are in the classpath
[
https://issues.jboss.org/browse/WELD-905?page=com.atlassian.jira.plugin.s...
]
Ales Justin resolved WELD-905.
------------------------------
Resolution: Out of Date
Re-open if still an issue with AS7.
@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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:30 p.m.
New subject: [JBoss JIRA] (WELD-905) @Alternative broken if multiple implementations are in the classpath
[
https://issues.jboss.org/browse/WELD-905?page=com.atlassian.jira.plugin.s...
]
Gerhard Petracek reopened WELD-905:
-----------------------------------
It's still broken (tested with AS7.1)
@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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:36 p.m.
New subject: [JBoss JIRA] (WELD-905) @Alternative broken if multiple implementations are in the classpath
[
https://issues.jboss.org/browse/WELD-905?page=com.atlassian.jira.plugin.s...
]
Gerhard Petracek updated WELD-905:
----------------------------------
Attachment: WELD-905.zip
this file contains the described example.
@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
Attachments: WELD-905.zip
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:16 p.m.
New subject: [JBoss JIRA] (WELD-905) @Alternative broken if multiple implementations are in the classpath
[
https://issues.jboss.org/browse/WELD-905?page=com.atlassian.jira.plugin.s...
]
Ales Justin reassigned WELD-905:
--------------------------------
Assignee: Marko Lukša
@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
Assignee: Marko Lukša
Priority: Critical
Attachments: WELD-905.zip
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:17 p.m.
New subject: [JBoss JIRA] (WELD-905) @Alternative broken if multiple implementations are in the classpath
[
https://issues.jboss.org/browse/WELD-905?page=com.atlassian.jira.plugin.s...
]
Marko Lukša commented on WELD-905:
----------------------------------
I've tested this on 7.1 and found that {{BeanA2}} plays no role here. Whether the
second bean archive is included in WEB-INF/lib or not, it is always {{BeanA}} that gets
injected into {{Page}}. And this appears to be the correct behavior according to section
5.1 of the spec:
{quote}
An alternative is not available for injection, lookup or EL resolution to classes or
JSP/JSF pages *in a module unless the module is a bean archive and the alternative is
explicitly selected in that bean archive*.
{quote}
Since the alternative is only selected in the first bean archive, and {{Page}} is located
in the war (and not inside the first bean archive), the injected bean should in fact be
{{BeanA}}. If you were to move {{Page}} into the first bean archive, only then would
{{BeanA1}} be injected into {{Page}}, since {{BeanA1}} is selected as an alternative only
in the first bean archive.
Can someone confirm this?
@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
Assignee: Marko Lukša
Priority: Critical
Attachments: WELD-905.zip
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:41 p.m.
New subject: [JBoss JIRA] (WELD-905) @Alternative broken if multiple implementations are in the classpath
[
https://issues.jboss.org/browse/WELD-905?page=com.atlassian.jira.plugin.s...
]
Gerhard Petracek commented on WELD-905:
---------------------------------------
that's right - with as7.1 the effect is different. removing module 2 doesn't lead
to a different behaviour (like before).
however, BeanA1 is in the same bean archive and it's configured as alternative.
the current behaviour is the 2nd interpretation of this part of the spec. and the 3rd+
behaviour i've seen with weld.
since the whole topic is also related to CDI-18 and the current behaviour is better than
everything i've seen in weld before, i'm ok with closing this ticket and keep the
behaviour as it is.
@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
Assignee: Marko Lukša
Priority: Critical
Attachments: WELD-905.zip
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:50 a.m.
New subject: [JBoss JIRA] (WELD-905) @Alternative broken if multiple implementations are in the classpath
[
https://issues.jboss.org/browse/WELD-905?page=com.atlassian.jira.plugin.s...
]
Marko Lukša resolved WELD-905.
------------------------------
Resolution: Cannot Reproduce Bug
@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
Assignee: Marko Lukša
Priority: Critical
Attachments: WELD-905.zip
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4423
days inactive
4727
days old
15 comments
6 participants
participants (6)
-
Ales Justin (Commented) (JIRA) -
Ales Justin (JIRA)
-
Gerhard Petracek (JIRA)
-
Marko Lukša (JIRA)
-
Pete Muir (JIRA)
-
Stuart Douglas (JIRA)