If there are Repositories that have Entities that are not annotated with @jakarta.nosql.Entity that should not cause a MappingException to be thrown by JNoSQL. JNoSQL should just ignore the entity/repository and allow it to be handled by the Jakarta Data provider that support the entity/repository.
Create an application that is backed by JNoSQL and another Jakarta Data provider.
Expected Results
JNoSQL should only be a provider for Jakarta Data repositories that use entities annotated with @jakarta.nosql.Entiity and should not attempt to validate/provide repository implementations for other repositories that may be backed by another Jakarta Data provider.
Which JNoSQL project the issue refers to?
JNoSQL (Core)
Bug description
If there are Repositories that have Entities that are not annotated with
@jakarta.nosql.Entitythat should not cause a MappingException to be thrown by JNoSQL. JNoSQL should just ignore the entity/repository and allow it to be handled by the Jakarta Data provider that support the entity/repository.https://github.com/eclipse/jnosql/blob/1cc14d14be62e90912c75c17dfbfda86c9551e59/jnosql-mapping/jnosql-mapping-reflection/src/main/java/org/eclipse/jnosql/mapping/reflection/ClassGraphClassScanner.java#L120-L129
JNoSQL Version
1.1.0
Steps To Reproduce
Create an application that is backed by JNoSQL and another Jakarta Data provider.
Expected Results
JNoSQL should only be a provider for Jakarta Data repositories that use entities annotated with
@jakarta.nosql.Entiityand should not attempt to validate/provide repository implementations for other repositories that may be backed by another Jakarta Data provider.Code example, screenshot, or link to a repository
No response