[weld-dev] Re: BasicInjectionTarget ignores injection points set by portable extension?
On Thu, Oct 17, 2024 at 9:11 AM Martin Kouba <mkouba(a)redhat.com> wrote:
On 17. 10. 24 17:13, Laird Nelson wrote:
> Why, then, does the InjectionTarget interface have a
> getInjectionPoints() method?
So that it's possible to access the metadata about all injection points
of a specific InjectionTarget.
Why, in this case, then, would Weld care at all, since I'm responsible for
injection? Why would it need to read this metadata that describes things
that it is not going to work on? (I still don't understand why
getInjectionPoints() exists on a producer if the producer is wholly
responsible for injection.)
In theory, an arbitrary injection point does not have to provide a
valid
member.
Could you explain more? Do you mean that
https://jakarta.ee/specifications/cdi/4.0/apidocs/jakarta.cdi/jakarta/ent...
could return null or a no-op or something else without violating the
contract? Where can I read more about that?
But again, the spec wording is clear - it's up to the
InjectionTarget
implementation.
Thanks; I see that now. I wish I fully understood why. To put it in
concrete terms, if org.jboss.weld.util.Beans had an injectInjectionPoints()
method alongside its injectFieldsAndInitializers() method Weld could work
with custom injection targets out of the box.
Fortunately Weld provides the InjectionServices plugin which has all the
information needed to permit this kind of enhancement, I think. Thanks for
your time.
L
Attachments:
- attachment.html (text/html — 2.3 KB)