Due to navigation caases, you page after GET request may be different from request to request, depend on application state. For bookmarkable links, best case to use redirect navigation options . May be, for such cases best solution will be save/restore request state for redirect, simulate single request processing for redirects ? After such processing, You will have right ( bookmarkable ) uri in browser for page. Second part for such solution can be ability for define "default" action methods for non-faces requested pages. In such, when re-visiting bookmarked page, in case of non-actual page client can be forward to different view ( as I see, such functions exist in Struts/Shale ).

" not submitting a form and loosing all JSF state but having a bookmarkable link? " - already exist in <h:outputLink > with nested <f:param >

Jesse Alexander (KBSA 21) :
to put it in a nutshell:

add GET-processing to JSF...

+100 ;-)

regards
Alexander
-----Original Message-----
From: Martin Marinschek [mailto:[EMAIL PROTECTED] Sent: Friday, January 27, 2006 10:35 AM
To: MyFaces Development
Subject: Bookmarking, History and JSF

Hi all,

I'm having ideas again. Must come from too much work with JSF ;)

My idea:

Bookmarking is a problem with JSF, right? Except you use h:outputLink,
but then there's this slight problem with not being in the action
system anymore ;)

Now, what do I want to be able to see in my history or to bookmark? I
want to bookmark simple pages, where state is not so important at all.
Or only a small portion of the state is important...

Those simple pages I usually refer to with an "action" attribute that
is put (as a string) directly on the <h:commandLink /> or
<h:commandButton/> tag, right?

Why not render out this action attribute as a parameter to the URL of
the link optionally, not submitting a form and loosing all JSF state,
but having a bookmarkable link?

The developer can decide then:
 - do I need this link to be bookmarked
- do I want this link to  use the plain old JSF posting system with
state-saving.

Enhancement: we could additionally render out params to this link as -
yes, right, params to the URL. So people can optionally build there
web-apps just like they were used to when JSF wasn't around.

Good idea - bad idea - better idea ;) ?

regards,

Martin

--

http://www.irian.at

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

Professional Support for Apache MyFaces

--
Alexander Smirnov
Software developer
Exadel Inc.
http://www.exadel.com/
mail-to:[EMAIL PROTECTED]

Reply via email to