Jakarta Data repository discovery

[gavinking]

Currently we say:

Exceptionally, the annotation jakarta.data.repository.Repository must be treated as a discoverable annotation type, even though it is not explicitly annotated @Discoverable.

I'm thinking that this is not quite enough, since it makes an implicit assumption that the Jakarta Data repository is deployed in the persistence unit, but application programs might want some other modular architecture.

I'm thinking it would be good to add some additional language that the EE container treats every Jakarta Data repository which depends on the persistence unit as a discoverable type of that persistence unit.

[njr-11]

How late would be acceptable for the persistence unit to be informed of the repository? We could potentially add a notification method to EntityHandler or its EntityManagerFactory (something like register(Class<?> repositoryClass)) and write a requirement for the Jakarta Data provider into the Jakarta Data spec that each EntityHandler that a repository uses must be notified of the repository interface via this method before the repository implementation uses the EntityHandler.