myfaces-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexandre Poitras" <alexandre.poit...@gmail.com>
Subject Re: wizard-style JSF application: looking for words of wisdom
Date Sat, 16 Sep 2006 22:28:36 GMT
What about Spring web flow? Shale dialog has burrowed A LOT from this
project (according to the authors themselves).

On 9/16/06, Julian Ray <julianjray@yahoo.com> wrote:
> We have several of these in our app and have a consistent approach using
> just Tomahawk. Each page of the wizard has a different backing bean (request
> scope) which inherits from a wizard class which manages forward/backward
> navigation etc. and access to a wizard-specific bean to store state. The
> state bean is managed using Tomahawk's saveState tag.
>
> The model works well and is very efficient. We use it for creating new
> objects as well as editing existing object -- you just have to be careful
> about how to initialize the state bean on the first page and managing page
> access such that the user could not type a URL to page n unless page n-1 has
> been completed.
>
> -----Original Message-----
> From: Gerald Müllan [mailto:bierbrauen@gmail.com]
> Sent: Saturday, September 16, 2006 8:16 AM
> To: MyFaces Discussion
> Subject: Re: wizard-style JSF application: looking for words of wisdom
>
> Yes, you can also use sandbox` conversation component to achieve a wizard.
>
> In the current application i am developing on, we use t:savestate in order
> to get a page-wide scope for our beans. The beans are special page-wizard
> beans which get a base wizard functionality from a wizard base class.
>
> The typical back-forward-end functionality works very well with this
> solution.
>
> cheers,
>
> Gerald
>
> On 9/15/06, William Huang <WHuang@intralinks.com> wrote:
> > then I think a nice solution is Andrew Robinson's method (JBoss Seam &
> > Facelets),  but instead of JBoss Seam, use tomahawk savestate.  I
> > think there is also a conversation jsf tag/component from tomahawk as
> well.
> >
> > William Huang
> > Product Development Team
> >
> >              "Henrik Bentel"
> >              <hbentel.ml@gmail
> >              .com>                                                      To
> >                                        "MyFaces Discussion"
> >              09/15/2006 12:08          <users@myfaces.apache.org>
> >              PM                                                         cc
> >
> >                                                                    Subject
> >              Please respond to         Re: wizard-style JSF application:
> >                  "MyFaces              looking for words of wisdom
> >                 Discussion"
> >              <users@myfaces.ap
> >                  ache.org>
> >
> >
> >
> >
> >
> >
> >
> > They both look like good alternatives except I'm stuck on java 1.4.2
> > and EE 1.3 (weblogic 8.1).
> > It seems they both require higher JDK/EE versions.
> >
> > -Henrik
> >
> >
> > On 9/15/06, Adam Brod <ABrod@intralinks.com> wrote:
> > >
> > > Check out JBoss Seam or the Apache Shale project.  They are both JSF
> > > frameworks with support for widard-like flows.
> > >
> > >  Adam Brod
> > >  Product Development Team
> > >
> > >
> > > "Henrik Bentel" <hbentel.ml@gmail.com> wrote on 09/15/2006 11:22:56 AM:
> > >
> > >
> > >  > Hi
> > >  >
> > >  > I'm developing a JSF webapp which works like a 'wizard' where the
> > > user  > steps though  > several pages(or steps). The main navigation
> > > control are links like  > 'next', 'previous', and 'cancel'.  I've
> > > done a couple of these  > 'wizard'-style apps, each very different
> > > in structure.
> > >  >
> > >  > I'm looking for suggestions for what you've found to work well in
> > > this  > type of application.
> > >  >
> > >  >
> > >  > My previous 2 weak attempts of a wizard-style app is as follows.
> > >  > My first app has one managed bean for the entire wizard with all
> > > > validation and wizard logic in that one bean(and supporting POJOs).
> > >  > Using one backing bean made it easier for reuse of page layout
> > > and  > navigation controls, and made it easy to skip steps
> > > dynamically at  > runtime. But it grew very large and not very pretty.
> > >  >
> > >  > My second app has one backing bean per 'step'. But I couldn't
> > > find an  > obvious way of reuse page layout and navigation controls
> > > across all  > the managed beans. So each page is bound to its own
> > > backing bean with  > 'next', 'previous' and 'cancel' action methods.
> > > And sometimes a  > backing bean had to know which page was the
> > > previous and the next  > step.
> > >  >
> > >  > Hope someone can help
> > >  >
> > >  > regards,
> > >  > Henrik
> > >
> > >  Disclaimer: This electronic mail and any attachments are
> > > confidential
> > and
> > > may be privileged. If you are not the intended recipient, please
> > > notify
> > the
> > > sender immediately by replying to this email, and destroy all copies
> > > of
> > this
> > > email and any attachments. Thank you.
> > >
> > >
> > >
> >
> > Disclaimer: This electronic mail and any attachments are confidential and
> may be privileged. If you are not the intended recipient, please notify the
> sender immediately by replying to this email, and destroy all copies of this
> email and any attachments. Thank you.
> >
> >
>
>
> --
> http://www.irian.at
>
> Your JSF powerhouse -
> JSF Consulting, Development and
> Courses in English and German
>
> Professional Support for Apache MyFaces
>
>

Mime
View raw message