playframework / playframework/play1
Make HibernateInterceptor replaceable
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.6k
- Forks
- 671
- Avg merge
- 12d 15h
- Merged PRs (30d)
- 1
Description
The (static) HibernateInterceptor needs to be configurable. Either through play plugin system or through injecting an own implementation of the hibernate interceptor. the latter is preferred as it will not introduce new PlayPlugin methods.
Background: If someone needs to integrate deeply with a process engine transaction handling can be tricky, and some additional events from hibernate need to be accessible.
Just some simple modifications arround that line would be great:
https://github.com/playframework/play1/blob/master/framework/src/play/db/jpa/JPAPlugin.java#L179
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in framework/src/play/db/jpa/JPAPlugin.java around line 179, where the static HibernateInterceptor is configured. Read how the interceptor is created and consider the preferred injection approach without adding PlayPlugin methods. Done means callers can provide their own interceptor while existing behavior remains available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, database
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100