well, I have just shortly skimmed through the article and I did not see that the issue regarding the back button has really been solved - what they propose is not to use the back button but to do the backward navigation server-side....
or did I miss some important information here? I don't see anything about clients, javascript, etc. in the article; that would be necessary if the server should get the information about the back-button... I still believe that the best and easiest solution to the back button problem is to use client side state saving, works like a charm! regards, Martin On Fri, 19 Nov 2004 09:19:19 +0100, Manfred Geiler <[EMAIL PROTECTED]> wrote: > Thanks for the info. > Did not have the time yet to study this solution in detail so I might > have missed something important. But rather than implementing the same > thing in MyFaces I would prefer a solution simliar to the Tiles > intergration. > WDYT? > > Manfred > > > > > niksa_os wrote: > > I have problem with backwards navigation in my jsf app. So, I search net > > for solution and I find this article > > http://www-106.ibm.com/developerworks/library/wa-webflow/?ca=dnt-546 > > > > "The WebFlow Navigation Manager framework (which I'll call WFNM for > > short) is a Web framework that focuses on problems that current > > frameworks, such as Struts or JavaServer Faces (see the Resources for > > links to both), do not manage. Rather than trying to reinvent the wheel, > > it complements and can be used in conjunction with these other > > frameworks, and can even be used with applications based on servlets and > > JSP pages alone. WFNM is distributed under the Lesser GNU Public > > License, and binaries containing WFNM code can thus be used in any > > commercial Web application." > > > > Maybe myFaces team can implement something like this, in the core of > > myFaces for backwards navigation! > > > > "Use the code > > The best way to start with the WFNM is to look at the sample provided > > with the framework itself at the project's Web site (see Resources): it > > is the complete scenario described in this article. It is largely > > self-explanatory and can be used as a template for developing other Web > > applications. The sample contains two different versions of the complete > > scenario shown above: the first is implemented using WFNM in conjunction > > with Struts, the second is implemented in conjunction with JavaServer > > Faces." > > > > What you (myFaces team) think about it? > > > > P.S. Do you know for other technique to manage backwards navigation > > within myFaces? > > >
