AnnotatedTypeConfigurator: easy recipe for configuring superclass fields?

[ljnelson]

I am doing horrible and unsightly things with a CDI extension and the Maven dependency resolution project known as maven-resolver.

The Maven part is uninteresting except that it makes use of an old dependency injection model known as Plexus.

In Plexus, what CDI would call a bean is annotated with @Component, and what CDI would call an injection point is annotated with @Requirement.

In the Maven codebase, there is a pattern where a @Component-annotated class will have a superclass whose private fields are annotated with @Requirement.  In the abstract, I'd like to configure these fields to have @Inject on them so that CDI will perform the dependency injection that Plexus used to.

Using an AnnotatedTypeConfigurator, I can of course get the fields of the @Component-annotated type (via fields() or filterFields()).  But I don't see any clean way to get access to the superclass' fields.

I am aware that I can take the "hard way" and bypass the configurator and use ProcessAnnotatedType#setAnnotatedType(AnnotatedType) instead, but I was hoping for an easier recipe. :-)  So: is there a way I'm overlooking to get access to the superclass' fields?  Should AnnotatedTypeConfigurator provide access to another AnnotatedTypeConfigurator representing its superclass?

[ljnelson]

Never mind! I see that the AnnotatedTypeConfigurator#filterFields() method does in fact return all fields from the entire type hierarchy.  A little unexpected, but I'll take it!

[manovotn]

Hmm, that sounds somewhat suprising.

However, AnnotatedTypeConfigurator#filterFields() makes use of AnnotatedType#getFields() which is supposed to return all annotated fields of given type.

So that might be why you get all of them.

Gotta try this with some dummy project to see for myself.

[manovotn]

Alright, I read CDI-697 too (was a bit too quick to answer here) and I am pretty sure the behavior is correct.

Basically, it is as I said - due to the usage of AnnotatedType#getFields() you get all the fields, even in supertypes.

But granted, it is not clear that AnnotatedTypeConfigurator#fields() will behave in the same manner.