There are plenty of applications where login is not required - catalog listings, search engine etc. Bookmarkings was not available with conventional applications platform until the internet and web browser came along and we started developing applications on it. Now that the functionality is here and the users have gotten used to it and demanding it - the question is really whether we want to preserve it in JSF.
Yee -----Original Message----- From: news [mailto:[EMAIL PROTECTED] On Behalf Of Werner Punz Sent: Friday, 28 October 2005 6:40 PM To: [email protected] Subject: Re: How to pass parameters between pages.. Bookmarking in real web applications, no matter being it jsf or non jsf is kindof problematic, you simply cannot really do it in a sane manner, to the the extensive usage of forms http post and other things. It does not make sense in most cases anyway, due to the fact that the user often has to go through extensive security layers often with a dedicated login page. In Webpages yes, but web applications are an entirely different issue, and probably having several dedicated bookmarking points with a dedicated filter to one of the points, in the application might be the way to go for you. Werner Lucio Piccoli wrote: > if u are going from page A - page B using a commandlink then u the <f:param> > > <h:commandLink immediate="true" action="#{BForm.detail}"> > <f:param name="username" value="#{summary.id}"/> > <h:outputText value="#{summary.id}"/> > </h:commandLink> > > > -lp > > >>>>Yee CN <[EMAIL PROTECTED]> 27/10/2005 7:12 pm >>> > > Hi, > > > > I have been wondering how to pass parameters between pages. > > > > In the jsp days I would encode it in the http request parameters. But with > JSF page navigation I guess I have to do it via the backing beans. > > > > Lets say the navigation is from A to B. A would need to call a method in B's > backing bean to give it the parameter. That is fine conceptually - however > the problem with this approach is then B's backing bean would need to be in > the session scope, which may not always be appropriate. > > > > Or maybe we should consider using ThreadLocal for parameter passing? This > approach is appealing has we don't have to do any cleaning up afterwards. Or > maybe a lightweight Backing bean specifically for the purpose of parameters > passing? > > > > Is there a best practice for this yet? > > > > Many thanks in advance. > > > > Yee > > > > > > > > > ********************************************************************** > This message has passed through an insecure network. > Please direct all enquiries to the message author. > ********************************************************************** > >
