8:25 a.m.
Martin Kouba created CDI-232:
--------------------------------
Summary: Relax requirements for built-in Instance
Key: CDI-232
URL: https://issues.jboss.org/browse/CDI-232
Project: CDI Specification Issues
Issue Type: Clarification
Affects Versions: 1.1.EDR1
Reporter: Martin Kouba
5.6.2. The built-in Instance
{quote}
The container must provide a built-in bean with:
* Instance<X> and Provider<X> for every legal bean type X in its set of bean
types,
* every qualifier type in its set of qualifier types,
{quote}
This type/qualifier requirements seem to be too strict. Maybe we should omit these and
instead force implementation to satisfy every injection point for every legal bean type
and corresponding qualifiers found in application... or something like that. I'm not
sure about the wording.
By the way Weld (2.0.0.Alpha2) does not fulfil these requirements at the moment.
--
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
1:17 p.m.
[
https://issues.jboss.org/browse/CDI-232?page=com.atlassian.jira.plugin.sy...
]
Pete Muir commented on CDI-232:
-------------------------------
I think the issue then is you can't look up an Instance for some other bean
dynamically...
Relax requirements for built-in Instance
----------------------------------------
Key: CDI-232
URL: https://issues.jboss.org/browse/CDI-232
Project: CDI Specification Issues
Issue Type: Clarification
Affects Versions: 1.1.EDR1
Reporter: Martin Kouba
5.6.2. The built-in Instance
{quote}
The container must provide a built-in bean with:
* Instance<X> and Provider<X> for every legal bean type X in its set of bean
types,
* every qualifier type in its set of qualifier types,
{quote}
This type/qualifier requirements seem to be too strict. Maybe we should omit these and
instead force implementation to satisfy every injection point for every legal bean type
and corresponding qualifiers found in application... or something like that. I'm not
sure about the wording.
By the way Weld (2.0.0.Alpha2) does not fulfil these requirements at the moment.
--
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
1:33 p.m.
[
https://issues.jboss.org/browse/CDI-232?page=com.atlassian.jira.plugin.sy...
]
Pete Muir updated CDI-232:
--------------------------
Fix Version/s: TBD
Relax requirements for built-in Instance
----------------------------------------
Key: CDI-232
URL: https://issues.jboss.org/browse/CDI-232
Project: CDI Specification Issues
Issue Type: Clarification
Affects Versions: 1.1.EDR1
Reporter: Martin Kouba
Fix For: TBD
5.6.2. The built-in Instance
{quote}
The container must provide a built-in bean with:
* Instance<X> and Provider<X> for every legal bean type X in its set of bean
types,
* every qualifier type in its set of qualifier types,
{quote}
This type/qualifier requirements seem to be too strict. Maybe we should omit these and
instead force implementation to satisfy every injection point for every legal bean type
and corresponding qualifiers found in application... or something like that. I'm not
sure about the wording.
By the way Weld (2.0.0.Alpha2) does not fulfil these requirements at the moment.
--
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.
[
https://issues.jboss.org/browse/CDI-232?page=com.atlassian.jira.plugin.sy...
]
Pete Muir commented on CDI-232:
-------------------------------
Martin, why do you think we need to do this?
Relax requirements for built-in Instance
----------------------------------------
Key: CDI-232
URL: https://issues.jboss.org/browse/CDI-232
Project: CDI Specification Issues
Issue Type: Clarification
Affects Versions: 1.1.EDR1
Reporter: Martin Kouba
Fix For: TBD
5.6.2. The built-in Instance
{quote}
The container must provide a built-in bean with:
* Instance<X> and Provider<X> for every legal bean type X in its set of bean
types,
* every qualifier type in its set of qualifier types,
{quote}
This type/qualifier requirements seem to be too strict. Maybe we should omit these and
instead force implementation to satisfy every injection point for every legal bean type
and corresponding qualifiers found in application... or something like that. I'm not
sure about the wording.
By the way Weld (2.0.0.Alpha2) does not fulfil these requirements at the moment.
--
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:08 a.m.
[
https://issues.jboss.org/browse/CDI-232?page=com.atlassian.jira.plugin.sy...
]
Jozef Hartinger commented on CDI-232:
-------------------------------------
I doubt there is an implementation that would be following this. What can be implied from
the spec says is that if you obtain the Bean<?> object for the built-in Instance
bean and call Bean.getTypes() you should get huge set of Instance<X> and
Provider<X> where X is every possible Java type that matches "2.2.1. Legal bean
types".
I think that this would not even be a finite set most of the time so typesafe resolution
cannot clearly work this way for the Instance bean.
Relax requirements for built-in Instance
----------------------------------------
Key: CDI-232
URL: https://issues.jboss.org/browse/CDI-232
Project: CDI Specification Issues
Issue Type: Clarification
Affects Versions: 1.1.EDR1
Reporter: Martin Kouba
Fix For: TBD
5.6.2. The built-in Instance
{quote}
The container must provide a built-in bean with:
* Instance<X> and Provider<X> for every legal bean type X in its set of bean
types,
* every qualifier type in its set of qualifier types,
{quote}
This type/qualifier requirements seem to be too strict. Maybe we should omit these and
instead force implementation to satisfy every injection point for every legal bean type
and corresponding qualifiers found in application... or something like that. I'm not
sure about the wording.
By the way Weld (2.0.0.Alpha2) does not fulfil these requirements at the moment.
--
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:10 a.m.
[
https://issues.jboss.org/browse/CDI-232?page=com.atlassian.jira.plugin.sy...
]
Jozef Hartinger edited comment on CDI-232 at 8/16/12 8:08 AM:
--------------------------------------------------------------
I doubt there is an implementation that would be following this. What can be implied from
the spec is that if you obtain the Bean<?> object for the built-in Instance bean and
call Bean.getTypes() you should get huge set of Instance<X> and Provider<X>
where X is every possible Java type that matches "2.2.1. Legal bean types".
I think that this would not even be a finite set most of the time so typesafe resolution
cannot clearly work this way for the Instance bean.
was (Author: jharting):
I doubt there is an implementation that would be following this. What can be implied
from the spec says is that if you obtain the Bean<?> object for the built-in
Instance bean and call Bean.getTypes() you should get huge set of Instance<X> and
Provider<X> where X is every possible Java type that matches "2.2.1. Legal bean
types".
I think that this would not even be a finite set most of the time so typesafe resolution
cannot clearly work this way for the Instance bean.
Relax requirements for built-in Instance
----------------------------------------
Key: CDI-232
URL: https://issues.jboss.org/browse/CDI-232
Project: CDI Specification Issues
Issue Type: Clarification
Affects Versions: 1.1.EDR1
Reporter: Martin Kouba
Fix For: TBD
5.6.2. The built-in Instance
{quote}
The container must provide a built-in bean with:
* Instance<X> and Provider<X> for every legal bean type X in its set of bean
types,
* every qualifier type in its set of qualifier types,
{quote}
This type/qualifier requirements seem to be too strict. Maybe we should omit these and
instead force implementation to satisfy every injection point for every legal bean type
and corresponding qualifiers found in application... or something like that. I'm not
sure about the wording.
By the way Weld (2.0.0.Alpha2) does not fulfil these requirements at the moment.
--
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:10 a.m.
[
https://issues.jboss.org/browse/CDI-232?page=com.atlassian.jira.plugin.sy...
]
Jozef Hartinger edited comment on CDI-232 at 8/16/12 8:09 AM:
--------------------------------------------------------------
I doubt there is an implementation that would be following this. What can be implied from
the spec is that if you obtain the Bean<?> object for the built-in Instance bean and
call Bean.getTypes() you should get a huge set of Instance<X> and Provider<X>
where X is every possible Java type that matches "2.2.1. Legal bean types".
I think that this would not even be a finite set most of the time so typesafe resolution
cannot clearly work this way for the Instance bean.
was (Author: jharting):
I doubt there is an implementation that would be following this. What can be implied
from the spec is that if you obtain the Bean<?> object for the built-in Instance
bean and call Bean.getTypes() you should get huge set of Instance<X> and
Provider<X> where X is every possible Java type that matches "2.2.1. Legal bean
types".
I think that this would not even be a finite set most of the time so typesafe resolution
cannot clearly work this way for the Instance bean.
Relax requirements for built-in Instance
----------------------------------------
Key: CDI-232
URL: https://issues.jboss.org/browse/CDI-232
Project: CDI Specification Issues
Issue Type: Clarification
Affects Versions: 1.1.EDR1
Reporter: Martin Kouba
Fix For: TBD
5.6.2. The built-in Instance
{quote}
The container must provide a built-in bean with:
* Instance<X> and Provider<X> for every legal bean type X in its set of bean
types,
* every qualifier type in its set of qualifier types,
{quote}
This type/qualifier requirements seem to be too strict. Maybe we should omit these and
instead force implementation to satisfy every injection point for every legal bean type
and corresponding qualifiers found in application... or something like that. I'm not
sure about the wording.
By the way Weld (2.0.0.Alpha2) does not fulfil these requirements at the moment.
--
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:18 a.m.
[
https://issues.jboss.org/browse/CDI-232?page=com.atlassian.jira.plugin.sy...
]
Pete Muir commented on CDI-232:
-------------------------------
Yes, ok, I see what you mean.
What's intended is that you can resolve a bean of type
Instance<any-legal-bean-type>, but I can see that's not exactly what's been
written down.
Relax requirements for built-in Instance
----------------------------------------
Key: CDI-232
URL: https://issues.jboss.org/browse/CDI-232
Project: CDI Specification Issues
Issue Type: Clarification
Affects Versions: 1.1.EDR1
Reporter: Martin Kouba
Fix For: TBD
5.6.2. The built-in Instance
{quote}
The container must provide a built-in bean with:
* Instance<X> and Provider<X> for every legal bean type X in its set of bean
types,
* every qualifier type in its set of qualifier types,
{quote}
This type/qualifier requirements seem to be too strict. Maybe we should omit these and
instead force implementation to satisfy every injection point for every legal bean type
and corresponding qualifiers found in application... or something like that. I'm not
sure about the wording.
By the way Weld (2.0.0.Alpha2) does not fulfil these requirements at the moment.
--
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
4519
days inactive
4613
days old
7 comments
3 participants
participants (3)
-
Jozef Hartinger (JIRA) -
Martin Kouba (JIRA)
-
Pete Muir (JIRA)