Fix #5885: generics break panache repo enhancer

[FroMage]

Do not enhance generic/abstract repos
Use proper generics resolution when looking up the repository type
arguments

Fixes: #5885

[FroMage]

@loicmathieu it's very possible you have the same bug in mongo-panache, and will need the same fix (do not enhance abstract/generic repos).

It's also possible that you have the same issue in your reactive-mongo-panache repo IF your entity base type is generic.

[geoand]

👍

[loicmathieu]

mongodb-panache and the future mongodb-panache-reactive suffers from the same bug.
If you don't have time to fix it in mongodb-panacheinside the same PR, can you open an issue for it ?

[FroMage]

If you don't have time to fix it in mongodb-panache inside the same PR, can you open an issue for it ?

I can do it in this PR, should be simple.

[FroMage]

Added test/fix for mongo too.

[loicmathieu]

LGTM

[FroMage]

Huh, so native test fails, due to who knows what, but I am already rebased on master.

[FroMage]

It passed after restart

[MartinX3]

@FroMage Here we have the problem, that a Repository listAll() call gives us every DataBase entry in every table.
As example we made a trainer and the call for courses gives us all trainer, too.

Kotlin

abstract class BaseRepository<T>(@Inject val entityManager: EntityManager) : PanacheRepositoryBase<T, UUID> {

@Dependent class TrainerRepository(entityManager: EntityManager) : BaseRepository<Trainer>(entityManager) {

@Dependent class CourseRepository(entityManager: EntityManager) : BaseRepository<Course>(entityManager) {

Is it a different bug which needs to get reported in a new issue ticket?

[FroMage]

@MartinX3 is this with the current master which has the fix? I think it's the same bug and it should be fixed.

[MartinX3]

@FroMage Thank you for your fast response.
We use the maven 1.1.0.final release in our company.
Nice to hear that it will get fixed :)
Will it be released as 1.1.1 or do we need to wait for 1.2.0 (which has no ETA?)

Thank you all for the fix. :)

[FroMage]

That's a question for @gsmet but IIRC 1.2 is planned for January.