Hi, I think the only thing missing is a "conversational" type of persistence. That is that the application state object and persisted link shouldn't be simply session persisted but at least session persisted with some kind of "flowkey" prefix so to separate different flows. This would imply also some flow/conversation control mechanism (start/restart/reset/getFlowKey) I was planning to do a similar thing for T4.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
