Hacker News new | ask | show | jobs
by fschoning 4 days ago
Helidon has its own transaction manager, but the real issue here is that EclipseStore does not support transaction management out the box. Java objects are modified in memory, but stored with an explicit store() call. So in your transaction rollback you just need to reload the original data from the storage using the EclipseStore Reloader, and overwrite the dirty copy in memory. You have to track yourself which Java objects may have been changed.
1 comments
exabrial 4 days ago
That'd be a neat CDI Extension actually! This path is well trodden with JPA so one could use the multitude of examples out there to implement this.

If you ever get corp funding to work on this, look me up. I'd love to come hack on it.

link
fschoning 1 day ago
:-) Will do.

I am looking into supporting LocalTransactions natively and its actually quite easy, so that might drop soon.

Also working on a full database based on eclipsestore called ZeroZ DB (zeroz4j-db). I might switch the web app development framework to use that, and that will give multi JVM capabilities and also txns out the box.

link