If your navigation rules imply a <redirect/> and you don't have redirect
tracker manager enabled (part of tomahawk), you woul indeed get 2
request from browser and 2 invocation of backing beans:

Browser: submit form (request 1)
JSF: Received, apply request values (eventually create on demand request
scoped beans), validate, execut action, get navigation rule, send a
"redirect" to new location to browser
Browser, gets the redirect rule, request the new location from JSF
(request 2)
JSF: receive a get, create view, eventually create request scoped beans
on demand, render response.

En l'instant précis du 18/12/07 22:10, brian.waskiewicz s'exprimait en
ces termes:
> I have a page which takes a request-scoped backing bean. I noticed that when
> the page is loaded the backing bean gets created twice, then when the form
> is submitted (using an h:commandButton with attached action) the bean gets
> created twice again and the backing method gets called twice. We're using
> myfaces, so we have the 1.2.0 myfaces JSF api and implementation on the
> classpath (Sun's reference implementation isn't part of the war).
>
> I'm pretty much at a loss on this, so any help would be great. Thanks.
>   


-- 
http://www.devlog.be (a belgian developer's logs)


Reply via email to