Skip to content

Conversation

@Ladicek
Copy link
Member

@Ladicek Ladicek commented Feb 4, 2026

This is done by specifying a class whose direct superclass type is a parameterization of TypeLiteral. In this case, the type argument to TypeLiteral is an expected type, not the class itself.

Fixes #936

This is done by specifying a class whose direct superclass type is
a parameterization of `TypeLiteral`. In this case, the type argument
to `TypeLiteral` is an expected type, not the class itself.
@manovotn
Copy link
Contributor

manovotn commented Feb 10, 2026

CDI meeting note (Feb 10): We discussed adding a javadoc example with the usage of this pattern.

On second thought, I am not sure doing this alone is enough. We'd have to add a "standard" usage example and then this one as a special case. Otherwise it would stand out as a go-to option which is not the message we want to send 🤷
WDYT @Ladicek?

@Ladicek
Copy link
Member Author

Ladicek commented Feb 11, 2026

I do intend to add two examples indeed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

allow @Registration.types() to specify parameterized bean types

3 participants