Mailing-List: contact dev-help@myfaces.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "MyFaces Development" <dev@myfaces.apache.org>
Received-SPF: pass (athena.apache.org: domain of martin.marinschek@gmail.com
 designates 64.233.182.190 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=gUkhcmMeKMrFbAuLvA5Fd49oiyyg3duceTXMxVWpeoAZNfizAt+drzf6vzzFN5Z8lFUe8ern7mZO7OgXZOcabCmPuCjZ50UZU7CfFvTduQIijU+m1yXmMM/6zWx9piFiZS6q4EAsmHVAmxDOl6KZTSb7Mc3GGmP9Lv9OQ3v7V0U=
Message-ID: <5a99335f0711090345u694d361qc327551d3f3df654@mail.gmail.com>
Date: Fri, 9 Nov 2007 12:45:49 +0100
From: "Martin Marinschek" <martin.marinschek@gmail.com>
To: "MyFaces Development" <dev@myfaces.apache.org>
Subject: Re: [ORCHESTRA] Spring-Webflow
In-Reply-To: <47343E3D.1070307@ops.co.at>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <5a99335f0711090016r207c6e96u15fbf1f73e6b459f@mail.gmail.com>
	 <47341B84.30400@ops.co.at>
	 <71235db40711090138y7c5aff54y8a5df525ed0a3d51@mail.gmail.com>
	 <5a99335f0711090201u1eb88f3bh721445eb6780c29c@mail.gmail.com>
	 <71235db40711090212w36463b35jb6943dba4f61523d@mail.gmail.com>
	 <5a99335f0711090232j164ec947l107838ff9714b5a3@mail.gmail.com>
	 <47343E3D.1070307@ops.co.at>

Hi Mario,

we are talking about navigation here, you about beans.

Problem:

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.

regards,

Martin

On Nov 9, 2007 12:02 PM, Mario Ivankovits <mario@ops.co.at> 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
>
>


-- 

http://www.irian.at

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

Professional Support for Apache MyFaces