Hi guys, Our web application will use the ADF Faces 11g JSF components as its UI toolkit, but no other parts of the ADF framework. From what I've read, ADF offers the same page flow scope as MyFaces Trinidad and seems mostly targeted at exchanging data between views in a multi-window support.
To me this seems similar to Orchestra's conversation.access scope. Both scopes use the HTTP session for storage and appends a URL parameter to identify the current conversation context / page flow in a multi-window context. Orchestra has a few advantages, including Spring custom scope support and intuitive scope cleanup. ADF doesn't offer out-of-the-box a Spring custom scope and its page flow cleanup strategy is still unclear to me. It's also not clear to me either whether the page flow scope is meant for conversation-type scoping rather than a simple data exchange strategy. In view of these elements, I'm considering using Orchestra to manage component scoping, but I'm wary of the interaction between the two frameworks. Are they meant to be used together, has anybody had any success in doing this? Am I mis-understanding the purpose of the page flow scope? Thanks all, GB -- View this message in context: http://www.nabble.com/-Orchestra--Conversation-scope-vs-ADF-page-flow-scope-tp22291888p22291888.html Sent from the MyFaces - Users mailing list archive at Nabble.com.
