I do not think this is totally true,
a http form get is only achievable by bypassing
jsf out of the box. Since all form handling
relies severely on http post (for many reasons)
A parametrized link however can be achieved even without bypassing jsf.
Theoretically you could write a form object which allows http get
but there are severe limitations and problems with a pure get, so no one
has done it so far.
Hubert Rabago schrieb:
> Jacob Hookom, in discussing JSF myths [1], claims that:
>
> "Also, JSF can handle GET requests just as easily as other frameworks.
> Because of JSF's
> managed bean (IoC container), you can do the same kinds of things as
> you can with
> WebWork -- from parameter assignment to backing beans. An example is
> linking from page
> to page where id's are passed -- you can go the same route as Struts
> or WebWork and just
> render "employee.jsf?id=#{emp.id}" -- you don't have to use stateful component
> communication between pages."
>
> Is there any truth to this? I thought the reason we had extensions
> like NonFacesRequestServlet [2] was because this wasn't supported by
> the core functionality?
>
> thanks,
> Hubert
>
> [1] http://virtuas.com/articles/webframework-sweetspots.html
> [2] http://wiki.apache.org/myfaces/InvokingJsfPagesWithStandardUrls
>
