7:11 a.m.
Clarify how alternatives are enabled
------------------------------------
Key: CDI-112
URL: https://issues.jboss.org/browse/CDI-112
Project: CDI Specification Issues
Issue Type: Clarification
Components: Beans
Affects Versions: 1.0
Reporter: Shane Bryzak
The spec is open to interpretation about how alternatives are enabled. One popular
interpretation is that alternatives must be enabled within the same bean archive that
contains the alternative bean. However, it might be worth considering the merit of
enabling an alternative from a deployment archive that contains the bean archive.
For example, suppose we have the following deployment archive:
foo.war
/WEB-INF
beans.xml
/lib
bar.jar
/META-INF
beans.xml
/com
/acme
AlternativeBean.class
It may be worth allowing AlternativeBean.class (a class annotated with @Alternative) to be
enabled by listing it in the <alternatives> section of foo.war/WEB-INF/beans.xml.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:57 a.m.
New subject: [JBoss JIRA] Updated: (CDI-112) Clarify how alternatives are enabled
[
https://issues.jboss.org/browse/CDI-112?page=com.atlassian.jira.plugin.sy...
]
Pete Muir updated CDI-112:
--------------------------
Fix Version/s: 1.1 (Proposed)
Clarify how alternatives are enabled
------------------------------------
Key: CDI-112
URL: https://issues.jboss.org/browse/CDI-112
Project: CDI Specification Issues
Issue Type: Clarification
Components: Beans
Affects Versions: 1.0
Reporter: Shane Bryzak
Fix For: 1.1 (Proposed)
The spec is open to interpretation about how alternatives are enabled. One popular
interpretation is that alternatives must be enabled within the same bean archive that
contains the alternative bean. However, it might be worth considering the merit of
enabling an alternative from a deployment archive that contains the bean archive.
For example, suppose we have the following deployment archive:
foo.war
/WEB-INF
beans.xml
/lib
bar.jar
/META-INF
beans.xml
/com
/acme
AlternativeBean.class
It may be worth allowing AlternativeBean.class (a class annotated with @Alternative) to
be enabled by listing it in the <alternatives> section of foo.war/WEB-INF/beans.xml.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:22 p.m.
New subject: [JBoss JIRA] Commented: (CDI-112) Clarify how alternatives are enabled
[
https://issues.jboss.org/browse/CDI-112?page=com.atlassian.jira.plugin.sy...
]
Richard Hightower commented on CDI-112:
---------------------------------------
Also this is a similar problem domain to web-fragments.xml versus web.xml in the Servlet
3.0 specification. I think we should apply the same rules and techniques.
<order><first><others/><first></order>. Or at least see if
what Servlet's does with web-fragments makes sense for beans.xml files in other jars
veruss the beans.xml file in the WAR, EAR, etc.
Clarify how alternatives are enabled
------------------------------------
Key: CDI-112
URL: https://issues.jboss.org/browse/CDI-112
Project: CDI Specification Issues
Issue Type: Clarification
Components: Beans
Affects Versions: 1.0
Reporter: Shane Bryzak
Fix For: 1.1 (Proposed)
The spec is open to interpretation about how alternatives are enabled. One popular
interpretation is that alternatives must be enabled within the same bean archive that
contains the alternative bean. However, it might be worth considering the merit of
enabling an alternative from a deployment archive that contains the bean archive.
For example, suppose we have the following deployment archive:
foo.war
/WEB-INF
beans.xml
/lib
bar.jar
/META-INF
beans.xml
/com
/acme
AlternativeBean.class
It may be worth allowing AlternativeBean.class (a class annotated with @Alternative) to
be enabled by listing it in the <alternatives> section of foo.war/WEB-INF/beans.xml.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:51 p.m.
New subject: [JBoss JIRA] Commented: (CDI-112) Clarify how alternatives are enabled
[
https://issues.jboss.org/browse/CDI-112?page=com.atlassian.jira.plugin.sy...
]
Mark Struberg commented on CDI-112:
-----------------------------------
Imo an <alternative> should be enabled for the whole 'slice' of classes the
BeanManager works for. See CDI-18. This is essential because in practice you cannot
_repack_ all you jars just to enable an alternative YyyService in those jars. The
<first> <others> turned out to be not flexible enough for lots of situations.
Thus I prefer an ordinal with a float value.
Clarify how alternatives are enabled
------------------------------------
Key: CDI-112
URL: https://issues.jboss.org/browse/CDI-112
Project: CDI Specification Issues
Issue Type: Clarification
Components: Beans
Affects Versions: 1.0
Reporter: Shane Bryzak
Fix For: 1.1 (Proposed)
The spec is open to interpretation about how alternatives are enabled. One popular
interpretation is that alternatives must be enabled within the same bean archive that
contains the alternative bean. However, it might be worth considering the merit of
enabling an alternative from a deployment archive that contains the bean archive.
For example, suppose we have the following deployment archive:
foo.war
/WEB-INF
beans.xml
/lib
bar.jar
/META-INF
beans.xml
/com
/acme
AlternativeBean.class
It may be worth allowing AlternativeBean.class (a class annotated with @Alternative) to
be enabled by listing it in the <alternatives> section of foo.war/WEB-INF/beans.xml.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:06 p.m.
New subject: [JBoss JIRA] Commented: (CDI-112) Clarify how alternatives are enabled
[
https://issues.jboss.org/browse/CDI-112?page=com.atlassian.jira.plugin.sy...
]
Pete Muir commented on CDI-112:
-------------------------------
Not sure what ordering has to do with this? What would ordering enablements achieve?
I think we should just fold this into CDI-18.
Clarify how alternatives are enabled
------------------------------------
Key: CDI-112
URL: https://issues.jboss.org/browse/CDI-112
Project: CDI Specification Issues
Issue Type: Clarification
Components: Beans
Affects Versions: 1.0
Reporter: Shane Bryzak
Fix For: 1.1 (Proposed)
The spec is open to interpretation about how alternatives are enabled. One popular
interpretation is that alternatives must be enabled within the same bean archive that
contains the alternative bean. However, it might be worth considering the merit of
enabling an alternative from a deployment archive that contains the bean archive.
For example, suppose we have the following deployment archive:
foo.war
/WEB-INF
beans.xml
/lib
bar.jar
/META-INF
beans.xml
/com
/acme
AlternativeBean.class
It may be worth allowing AlternativeBean.class (a class annotated with @Alternative) to
be enabled by listing it in the <alternatives> section of foo.war/WEB-INF/beans.xml.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
2 a.m.
New subject: [JBoss JIRA] Commented: (CDI-112) Clarify how alternatives are enabled
[
https://issues.jboss.org/browse/CDI-112?page=com.atlassian.jira.plugin.sy...
]
Richard Hightower commented on CDI-112:
---------------------------------------
RE: The <first> <others> turned out to be not flexible enough for lots of
situations. Thus I prefer an ordinal with a float value.
Hmmm.. Ok.
Clarify how alternatives are enabled
------------------------------------
Key: CDI-112
URL: https://issues.jboss.org/browse/CDI-112
Project: CDI Specification Issues
Issue Type: Clarification
Components: Beans
Affects Versions: 1.0
Reporter: Shane Bryzak
Fix For: 1.1 (Proposed)
The spec is open to interpretation about how alternatives are enabled. One popular
interpretation is that alternatives must be enabled within the same bean archive that
contains the alternative bean. However, it might be worth considering the merit of
enabling an alternative from a deployment archive that contains the bean archive.
For example, suppose we have the following deployment archive:
foo.war
/WEB-INF
beans.xml
/lib
bar.jar
/META-INF
beans.xml
/com
/acme
AlternativeBean.class
It may be worth allowing AlternativeBean.class (a class annotated with @Alternative) to
be enabled by listing it in the <alternatives> section of foo.war/WEB-INF/beans.xml.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:31 a.m.
New subject: [JBoss JIRA] Closed: (CDI-112) Clarify how alternatives are enabled
[
https://issues.jboss.org/browse/CDI-112?page=com.atlassian.jira.plugin.sy...
]
Pete Muir closed CDI-112.
-------------------------
Resolution: Partially Completed
Merged into CDI-18
Clarify how alternatives are enabled
------------------------------------
Key: CDI-112
URL: https://issues.jboss.org/browse/CDI-112
Project: CDI Specification Issues
Issue Type: Clarification
Components: Beans
Affects Versions: 1.0
Reporter: Shane Bryzak
Fix For: 1.1 (Proposed)
The spec is open to interpretation about how alternatives are enabled. One popular
interpretation is that alternatives must be enabled within the same bean archive that
contains the alternative bean. However, it might be worth considering the merit of
enabling an alternative from a deployment archive that contains the bean archive.
For example, suppose we have the following deployment archive:
foo.war
/WEB-INF
beans.xml
/lib
bar.jar
/META-INF
beans.xml
/com
/acme
AlternativeBean.class
It may be worth allowing AlternativeBean.class (a class annotated with @Alternative) to
be enabled by listing it in the <alternatives> section of foo.war/WEB-INF/beans.xml.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:53 p.m.
New subject: [JBoss JIRA] (CDI-112) Clarify how alternatives are enabled
[
https://issues.jboss.org/browse/CDI-112?page=com.atlassian.jira.plugin.sy...
]
Pete Muir resolved CDI-112.
---------------------------
Fix Version/s: (was: 1.1 (Proposed))
Resolution: Duplicate Issue
Clarify how alternatives are enabled
------------------------------------
Key: CDI-112
URL: https://issues.jboss.org/browse/CDI-112
Project: CDI Specification Issues
Issue Type: Clarification
Components: Beans
Affects Versions: 1.0
Reporter: Shane Bryzak
The spec is open to interpretation about how alternatives are enabled. One popular
interpretation is that alternatives must be enabled within the same bean archive that
contains the alternative bean. However, it might be worth considering the merit of
enabling an alternative from a deployment archive that contains the bean archive.
For example, suppose we have the following deployment archive:
foo.war
/WEB-INF
beans.xml
/lib
bar.jar
/META-INF
beans.xml
/com
/acme
AlternativeBean.class
It may be worth allowing AlternativeBean.class (a class annotated with @Alternative) to
be enabled by listing it in the <alternatives> section of foo.war/WEB-INF/beans.xml.
--
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:53 p.m.
New subject: [JBoss JIRA] (CDI-112) Clarify how alternatives are enabled
[
https://issues.jboss.org/browse/CDI-112?page=com.atlassian.jira.plugin.sy...
]
Pete Muir reopened CDI-112:
---------------------------
Clarify how alternatives are enabled
------------------------------------
Key: CDI-112
URL: https://issues.jboss.org/browse/CDI-112
Project: CDI Specification Issues
Issue Type: Clarification
Components: Beans
Affects Versions: 1.0
Reporter: Shane Bryzak
The spec is open to interpretation about how alternatives are enabled. One popular
interpretation is that alternatives must be enabled within the same bean archive that
contains the alternative bean. However, it might be worth considering the merit of
enabling an alternative from a deployment archive that contains the bean archive.
For example, suppose we have the following deployment archive:
foo.war
/WEB-INF
beans.xml
/lib
bar.jar
/META-INF
beans.xml
/com
/acme
AlternativeBean.class
It may be worth allowing AlternativeBean.class (a class annotated with @Alternative) to
be enabled by listing it in the <alternatives> section of foo.war/WEB-INF/beans.xml.
--
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
4266
days inactive
4782
days old
8 comments
4 participants
participants (4)
-
Mark Struberg (JIRA) -
Pete Muir (JIRA)
-
Richard Hightower (JIRA)
-
Shane Bryzak (JIRA)