myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martin Marinschek" <>
Subject Re: [ORCHESTRA] Spring-Webflow
Date Fri, 09 Nov 2007 11:45:49 GMT
Hi Mario,

we are talking about navigation here, you about beans.


there is a wizard for editing a person - you can start this wizard
from the person-list, but also from the company list. After you have
finished editing the person, you want to return to the list you
started at. How do you configure this?

Its definitely a good idea to also support a managed bean per wizard,
that's for sure.



On Nov 9, 2007 12:02 PM, Mario Ivankovits <> wrote:
> Hi!
> I am not sure if I talk about the same, but ....
> In Orchestra it is all about beans. What would be nice is, if we could
> define a page-flow (state A) having it's own set of beans and being able
> to enter the page-flow (state B) again and having a new set of beans
> then (effectively the same bean/el names but the views will see
> different instances). Once state B finished state A will be reactivated
> again.
> Is this what we would like to have?
> For this, we need an additional configuration on the conversation ...
> maybe a start to have a conversation configuration at all:
> <conversation name="conversationA" group="orderState" />
> <conversation name="conversationB" group="orderState" />
> Now, with a simple API (for now)
> ConversationManager.getInstance().interruptState("orderState");
> ConversationManager.getInstance().invalidateState(String)
> ConversationManager.getInstance().resumeState(String)
> List<String> states =
> ConversationManager.getInstance().getInterruptedStates("orderState");
> The idea is to group conversations together and then to allow to
> interrupt/resume this group of conversations.
> Or did I understand something wrong?
> Ciao,
> Mario


Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German

Professional Support for Apache MyFaces

View raw message