Enlist repository parameterized types for reflection

[loicmathieu]

Fixes #6324

Enlist for relfection types parameters from interfaces and super classes.
This fixes the issue with the repository implementation where the repository type parameter (it should be the MongoDB persisted class) is not registered for reflection so it can fails if not direct usage is made that GraalVM can be aware of.

I didn't climb up the hierarchy of interfaces and super classes so it's still possible to have relfection issue for complex type hierarchies. I don't now if it worth it to implement it.

[gsmet]

Can you fix the commit message? relfection. Thanks.

[loicmathieu]

@gsmet commit message updated

Commit message fixed.

[gsmet]

We need to take into account hierarchy of superclasses. It happens and dealing with the superclass only is clearly not sufficient.

Or did I miss something?

[machi1990]

We need to take into account hierarchy of superclasses. It happens and dealing with the superclass only is clearly not sufficient.

Or did I miss something?

+1 with @gsmet here

[loicmathieu]

@gsmet hierarchy of super classes where the direct super classes is not the parameterized one seems to be not very common but I can handle it.
But this will need to wait for a few days ...

[loicmathieu]

@gsmet @machi1990 I climb up the hierarchy of super types in the PR.

Comments addressed.

[gsmet]

I will let @FroMage check that one and decide of its fate :).

[FroMage]

I don't understand this PR. The test you added is for when an entity type is never registered via reflection. This can only happen for Mongo, right? And only because you don't have an equivalent to @Entity that ORM uses to register those types. So for Mongo they become "unknown" unless they extend MongoPanacheEntity.

So, perhaps you should have a @MongoEntity annotation?

Alternately, what you want to do is use JandexUtil.resolveTypeParameters(DotName.createSimple(userRepoSubclassName), DotName.createSimple(MongoPanacheRepositoryBase.class.getName()), index) and get the right type parameter that points to the entity.

[loicmathieu]

@FroMage yes, when you define "mongodb entities" it's not mandatory to add the @MongoEntity annotation that only exist to define the database name (if not comming from application.properties) and the collection name (by default the name of the class).

We can ask to always add the annotation, but as it's not enforced inside the framework, situations will always exist where a user will not add it ...

I will refactory with JandexUtil.resolveTypeParameters().

[FroMage]

We can ask to always add the annotation, but as it's not enforced inside the framework, situations will always exist where a user will not add it ...

Well, you can enforce it ;)

It would be more consistent with ORM, but on the other hand this appears to be the first use-case for requiring it, and we can solve it by scanning type params, so probably we can keep that strategy for now and keep an eye out for new use-cases that would require that annotation.

[loicmathieu]

@FroMage updated with the usage of JandexUtil.resolveTypeParameters()

[FroMage]

Look @geoand we're all using this method now :)

[geoand]

Excellent, you all know who to direct your rage at if things don't work :P

[loicmathieu]

@gsmet ready to be merged :)

[loicmathieu]

There is an SO question about it: https://stackoverflow.com/questions/59722717/problem-with-native-image-in-quarkus-and-mongopanache

[geoand]

Let's merge