shadogray commented on PR #135: URL: https://github.com/apache/deltaspike/pull/135#issuecomment-1750392555
1) in the most restrictive - and quite appropriate - setting (discovery-mode=annotated) the annotations would be necessary. WildFly-29 moved to Weld-5 which according to documentation reflects this estimation: ` Migration from Weld 4.0 to 5.0 Weld 5 is a compatible implementation of Jakarta CDI 4.0[...] Empty beans.xml discovery mode CDI 4 changes the default discovery mode used for empty beans.xml - it is now **annotated** mode. ` 2) CriteriaSupportHandler already had the annotation, why not all DelegateQueryHandlers? 3) the factual observation in an application on WildFly-29.0.1 shows: ` org.apache.deltaspike.data.api.QueryInvocationException: Failed calling Repository: [Repository=x.y.z.EntityRepository,entity=x.y.z.Entity,method=**findAll**,exception=class org.apache.deltaspike.data.api.QueryInvocationException,message=Failed calling Repository: [Repository=x.y.z.EntityRepository,entity=x.y.z.Entity,method=**findAll**, at deployment.archive-web.war//org.apache.deltaspike.data.impl.handler.QueryHandler.process(QueryHandler.java:163) at deployment.archive-web.war//org.apache.deltaspike.data.impl.handler.QueryHandler.invoke(QueryHandler.java:130) ` There is exactly one reason, that **findAll** cannot be invoked on a Repository: the EntityRepositoryHandler is not evaluated by DelegateQueryHandler because lookup() doesn't find the Bean. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@deltaspike.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org