I would like to share some ideas before I start working on a new version of the Store: 1) Actually we have two stores, one that works inside Spring and one standalone. I would like to refactor and have only one store that can be used in both configurations. 2) The object model is well done, with relationship between Entry, CurrentStep and HistoryStep, but then this is not implemented in the HibernateMapping file, so I think we should fix this and navigate object starting from Entry. Told this two other considerations: a) Navigating object can be slower than queries at first, but I would like to think that in a Session bound to a request I will use OSWorkflow more than once. If not the application is so simple that should not have performance issues. b) Not regression: conceptually is the same, but then pratically navigating objects can give others results (I think that these are more accurate than query, but anyway can be different !!!!) 3) What about versioning object for optimistic locking support ? 4) I read http://jira.opensymphony.com/browse/WF-343, very interesting concepts inside but I don't think we need an interface that externalize all that for our stores. These should only USE the Sessions and never decide about transaction management. But this is an open question. Please let me know what do you think. Ciao.

"Ci sono 10 tipologie di persone, quelli che capiscono il binario e quelli che
non lo capiscono."