[Beankeeper-discussion] Are persistent user transactions possible with BeanKeeper?

[Daniel F. <da...@di...>]

Hi,

having reviewed quite a number of Java persistence solutions I think BeanKeeper 
is by far the easiest and cleanest (but yet very powerful) solution. I was 
especially taken with the full versioning concept which would be really helpful 
in my application.

But after reading the tutorial and the docs I'm still not sure: Are
persistent user transactions possible with BeanKeeper? I would like to make even 
non-completed transactions to survive an application restart, s.t. users can 
resume working with this transactions (after e.g. a server restart).

This would require to make the non-completed transactions somehow persistent - 
but without sacrificing the transaction isolation of course (if user X has such 
a non-completed transaction open no other user should see the changes done 
inside it).


Yours,
Daniel