A FormAction with a flow-scoped form backing object is a nice way to load a domain object using Hibernate and modify it over the course of a flow. It's natural that at the end of the flow, the object could then be submitted to Hibernate for persistence.
The unfortunate truth of the matter is that keeping a detached object in the flow scope and attempting to reassociate it with another Hibernate Session can be a difficult proposition.
The "Long Session" is often billed as the answer to this problem. Elsewhere in these forums Spring users have been asking about Hibernate Sessions that span for the length of an application transaction and the answer always seems to be: "but when will we know at what point to close the Hibernate Session?"
Does SWF alleviate this issue by adequately demarcating the beginning and the end of an application transaction? With SWF as a first class member of the Spring family is it conceivable that we'll see a long session implementation that relies on flows?