Extending SimpleJpaRepository (fixing problems in JPA spec)

[bjconlan]

I'm currently implementing a CascadeBulkDeleteJPARepostory to rectify a problem we are having with bulk deletes not removing @EmbeddedCollections. This is a well known problem (see http://stackoverflow.com/questions/3903202/how-to-do-bulk-delete-in-jpa-when-using-element-collections) and am overwriting the SimpleJPARepository to fix such a problem (temporarily just by performing deleteAll(Collection) at this stage). But I would find it beneficial to have access to the variables set by the constructor (at least in 1.0.0.M2).

Now obviously I currently maintain a reference to the objects in my implementation but providing a:

EntityManger getEntityManager()
and
JpaEntityInformation<T, ID> getEntityMetadata()

in the SimpleJPARepostory would be quite useful for such cases.

Thanks & great work.

[bjconlan]

'just by performing deleteAll(Collection)' that should be: I'm using the existing 'SimpleJPARepository.delete(Iteratable) inside the overriden deleteAll method.' It's hardly a pretty solution but I plan on parsing entity meta data at a later date.

[gregturn]

This appears to be a JPA-specific issue which is currently NOT SUPPORTED (read the updated comments on the linked SO response).

However, according to https://hibernate.atlassian.net/browse/HHH-5529, this has been has been added to Hibernate 6. However, there are a multitude of issues that bar us from adopting HIbernate 6 at this point in time.

Please feel free to revisit whenever you are able to adopt Hibernate 6 and see if this issue is still a problem.