The WebFlow docs state that persistence management is one of the major features of the most recent release (WebFlow Milestone 1): http://www.springframework.org/node/510
See the section: Web Flow 2.0 M1 New and Noteworthy It's good to head that you're familiar with WebFlow; I have been looking at it recently and intend to create a Wiki page comparing it against Orchestra as there is definitely some overlap. If you could take some time to look at that page (when it's done) and correct it that would be great... Cheers, Simon ---- Martin Marinschek <[EMAIL PROTECTED]> schrieb: > I wouldn't call spring-webflow too complicated in comparison to > Orchestra - but what you can't do with spring-webflow is to handle the > underlying JPA-persistence context out of the box, you can do that > with Orchestra. > > regards, > > Martin > > On 9/28/07, Simon Kitching <[EMAIL PROTECTED]> wrote: > > See here for information about conversations: > > http://myfaces.apache.org/orchestra/myfaces-orchestra-core/conversation.html > > > > If all you want is Spring DI and AOP for your beans, then you don't need > > Orchestra. However Spring core doesn't give you conversation scopes by > > default. > > > > Copnversation scopes are *really really* useful, however, and many projects > > are looking at providing conversation scopes in some way. Spring WebFlow is > > one example, but it seems quite complicated to me; IMO Orchestra is simpler > > to use with JSF. > > > > Regards, Simon
