[weld-dev] Re: BasicInjectionTarget ignores injection points set by portable extension?
On Thu, Oct 17, 2024 at 1:43 AM Matej Novotny <manovotn(a)redhat.com> wrote:
> The injection point so added is one of my choosing and it does
not
matter why I chose it. It honors the InjectionPoint contract. My intention
is that this is something that CDI should "fill".
What exactly should CDI do with this injection point in your opinion?
Given a class based beans with some fields (just to keep it simple), you
can modify the set of injection points and add an extra IP of type Foo that
wasn't present before.
I'm trying to do two things:
1. Exactly what you say here: I am trying to programmatically add an
unannotated field (the field is of course in the class) to the set of
injection points Weld will use natively
2. Let Weld do injection natively on the set of injection points I have so
described: I'm reporting the injection points I want filled; Weld knows how
to fill injection points; I want it to do its thing
I feel sheepish saying this but it's true: I don't know how to do (1)
without, for example, programmatically adding the @Inject annotation at,
say, ProcessAnnotatedType time; for various reasons I don't want to do it
that way. What's another way? I don't see any methods that would help me at
ProcessBeanAttributes, ProcessBean, ProcessManagedBean, etc. time.
Apologies if I'm missing something obvious.
Best,
Laird
Attachments:
- attachment.html (text/html — 1.8 KB)