[cdi-dev] Specializing producer methods & qualifiers
Jozef Hartinger
jharting at redhat.com
Tue Apr 14 02:26:11 EDT 2015
Hi Christian,
yes, the specializing producer inherits all the qualifiers of the
specialized producer. Furthermore, if the specialized producer had
defined a name, this would have been inherited as well (even without
explicit declaration on MyExtendedProducer.produce()). See
http://docs.jboss.org/cdi/spec/1.2/cdi-spec.html#direct_and_indirect_specialization
for details.
Jozef
On 04/14/2015 06:13 AM, Christian Kaltepoth wrote:
> Hey all,
>
> I've a question regarding specializing qualified producer methods. It
> would be great to get your opinion on this.
>
> Imaging this producer method:
>
> public class MyProducer {
> @Produces
> @MyQualifier
> public Something produce() {
> // ...
> }
> }
>
> Now imagine the producer method is specialized like this:
>
> public class MyExtendedProducer extends MyProducer {
> @Override
> @Produces
> @Specializes
> public Something produce() {
> // ...
> }
> }
>
> Please not that I NOT added @MyQualifier to the specializing producer
> method.
>
> Now for this injection point:
>
> @Inject
> @MyQualifier
> private Something something;
>
> What is expected to happen according to the spec? Will the specialized
> producer be used or not?
>
> Thanks
>
> Christian
>
>
> --
> Christian Kaltepoth
> Blog: http://blog.kaltepoth.de/
> Twitter: http://twitter.com/chkal
> GitHub: https://github.com/chkal
>
>
>
> _______________________________________________
> cdi-dev mailing list
> cdi-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/cdi-dev
>
> Note that for all code provided on this list, the provider licenses the code under the Apache License, Version 2 (http://www.apache.org/licenses/LICENSE-2.0.html). For all other ideas provided on this list, the provider waives all patent and other intellectual property rights inherent in such information.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20150414/25b037a6/attachment.html
More information about the cdi-dev
mailing list