[cdi-dev] RequestScoped and Injection Points
John D. Ament
john.d.ament at gmail.com
Tue Sep 6 20:10:21 EDT 2011
Was wondering if you could help me understand rationale. In request scoped
objects, when you create a producer method that creates request scoped
instances, why is there no access to the underlying injection point?
Let's say that you have a qualifier with a single String value attribute
that is nonbinding; let's say @JmsDestination. You have the following
@Inject @JmsDestination("jms/MyQueue") MessageProducer queueProducer;
@Inject @JmsDestination("jms/MyTopic") MessageProducer topicProducer;
In this case, two distinct MessageProducers should be injected. The CDI
container should be able to differentiate the two, since they have different
values on the qualifier. However, CDI disallows this since the producer
methods used to create them would not have access to the injection point.
If a second injection point is found, CDI should return the same instance.
I hope it doesn't sound like I'm babbling, but I wanted to put the question
out there to see if it's something that could be addressed.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the cdi-dev