CDI and JPA integration for Jakarta EE 11 needs FAT tests and bean destruction methods #32788
Description
We now have a beta feature that meets the new requirements of the EE 11 sepc for CDI and JPA integration and passes the TCK.
However before we can say this is good we need to first identify what, if any, cleanup methods must be invoked when one of the injected JPA object is cleaned out.
And secondly write FAT tests, there's a lot, and I do mean a lot, of interactions that the TCK does not cover.
[ ] When injecting EntityManagers, the default scope is TransactionScoped. We need to test with both a shorter scope. The test must ensure that EntityManager behaves correctly for the full duration of the scope and does not live longer than it should.
[ ] As above, but with a longer scope.
[ ] A test to ensure we can inject two EntityManagers defined in the same Persistence Unit, one with a qualifier and one with no qualifiers.
[ ] A test that injects and uses the EntityManager in multiple places and ensures it works as expected.
I am certain there are more that people with more JPA knowledge than me can think of.