[CAUSEWAY-2799] JPA: Framework caches and does not re-read changed state from the database.

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 2.0.0-M5
• Fix Version/s: 2.0.0-M6
• Component/s: Persistence JPA
• Assignee: Daniel Keir Haywood
• Reporter: Daniel Keir Haywood
• Created: 15/Jul/21 16:35
• Updated: 25/Aug/21 14:33
• Resolved: 26/Jul/21 12:04

Description

to reproduce:

• run up JPA simpleapp
• save an object
• using h2 console, update the name manually
• reload the object through the UI (eg click on the title)  - the change is not picked up, ie the database is not read.

 

~~~~

It seems that we use 

the symptom seems to be that we cache EntityManager's in JpaContext, which might be ok if they are proxied thread-locals; however the underlying aren't disposed of.

We notice that EclipseLink creates a "NoServerPlatform", meaning that it doesn't recognise us as being in a container.

We also notice that JPA creates an LocalContainerEntityManagerFactoryBean, whereas perhaps it should create a LocalEntityManagerFactoryBean.  https://stackoverflow.com/a/6157339/56880 

some docs:

https://www.eclipse.org/eclipselink/documentation/2.6/solutions/testingjpa001.htm

https://www.baeldung.com/jpa-hibernate-persistence-context - we want to use "transaction-scoped" persistence context rather than "extended" ... and we are, I think.