Hi Maciej, I'm curious about exactly what you are trying to achieve.
Orchestra provides a number of new scopes. Just like * request scope, or * session scope there are also * the scope of conversation "foo" * the scope of conversation "bar" * etc There cannot be two simultaneous copies of the "request" or "session" scopes, and neither can there be (yet) simultaneous copies of an orchestra-created scope. And neither is there any concept in either case of "selecting the current scope". Session scope is always active, and so are all of the conversation scopes. Looking up a bean by name will look through all the known scopes and return the bean wherever it is - request, session, or otherwise. I have had a requirement in a past project for someone to start editing a "user details" screen, then click on a link to a related user (eg "supervisor") and see that user's details, then use a breadcrumb to go back to the original user details and finish editing. In that case the screens were truly "re-entrant" and so it was necessary to have two copies of the backing beans for that view. I would have thought that was a fairly rare scenario. Is that the kind of scenario you have to deal with? Or is it something else? Orchestra probably *can* handle the above setup without too much complexity. Currently it keeps a map of conversations keyed by conversation name. When looking up a bean it first finds out (from the Spring file) what conversation-name it is associated with, then gets the bean from the conversation. Maybe if the map instead held a stack of conversations with a particular name, and only looked in the top conversation on the stack then user code could "push" a fresh conversation instance and pop it off later. I'm still not sure it is a high-priority issue though... The other option is to create a whole new "conversation context", where all of the conversations are new. There is no easy way to communicate between contexts though... Regards, Simon ---- Maciej Swinarski <[EMAIL PROTECTED]> schrieb: > > Are you trying to allow the user to navigate within the same set of > > pages but with different data? > > yes, thats what I m trying to do; > > > Then, this is not supported by Orchestra yet. > > :( > > thanx > > mac
