Hi Quintin, Hi Francescon, Quoting Quintin:
> One way to do it is mark all your navigation for redirect .....
That's possible. But you still have two major drawbacks: - Your request-scope bean-data get lost if you use the redirect navigation - You still can't bookmark and crawl all those pages, because parameters are not shown in the url and the first JSF request contains always "empty data" Quoting Francesco:
.....We obtained this result mainly by using outputLinks instead of commandLinks for passing parameters to pages.
Ok, this seems to work. ;) But then, what is the advantage of using JSF when using outputLinks? You are leaving the typicall JSF life-cycle and therefore the nice JSF features. It's comparable to use the good old MVC style... My conclusion: --------------------- - JSF/myfaces shouldn't be used when building a public available web-application that requires bookmarking and in particular indexing through search engines like google. - JSF/myfaces makes sense and helps a lot if you have to implement a closed and in generall login protected application that makes heavy use of forms and dynamic pages (e.g. if you use Ajax you also have these problems with bookmarking and searchengines) For me its out of all reason why the designer of JSF ignore the fundamental requirement of being web-conform. It had have to be a major requirement to return adequate URLs on JSF requests?! Another question: Why haven't the smart people of Apache myfaces present a easy to use solution for this? It would be very nice if the myfaces JSF implementation presents a extension which guarantees nice URLs (and therefore Bookmarking and search-engine compatibility). I'm sure that a working myfaces extension will be integrated in the JSF spec in future. But it doesn't seems to be that easy... ;) Greetings Chrisi
