[
https://issues.jboss.org/browse/CDI-590?page=com.atlassian.jira.plugin.sy...
]
Romain Manni-Bucau commented on CDI-590:
----------------------------------------
[~mkouba] yes. Suppose you have a configuration library or another IoC you want to
integrate with for instance. In such cases you often have
SuperFrameworkFactory.getBean(Type, Annotation, OtherParamLibSpecific) and you just can to
call this building the parameters from the InjectionPoint. Today the only solution with
CDI is to build an extension where you would just produce the bean and ensure it is not
ambiguous using a qualifier.
Provide a way to produce any type in a producer
-----------------------------------------------
Key: CDI-590
URL:
https://issues.jboss.org/browse/CDI-590
Project: CDI Specification Issues
Issue Type: Epic
Reporter: Romain Manni-Bucau
Note: this is a follow up "adding generic producers to CDI 2.0?" thread on the
list
It is common to rely on a subsystem (another IoC, a coercing system, ...) to produce
values. Today a producer can't say "I produce anything in a safe" manner.
Idea would be for injection point aware producers with a qualifier to producer Object and
match all types.
It needs another flag (can be in @Qualifier or another annotation it is not really
important) to say "I produce safely any type".
I did a PoC on github:
https://github.com/rmannibucau/generic-producer-cdi but think it
can be a nice feature of CDI 2.0 since it would avoid users to have to dig into extensions
for several simple cases (configuration, bridge to other IoC...)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)