Re: JSF flaw

[Dave]

I am using server side saving. If I use client side, my concern is performance and network traffic. Server side saving is using memory, no serialization going on.

Simon Kitching <[EMAIL PROTECTED]> wrote:

Just for anyone who might be interested, I was reading the JSF 1.2 spec
today, and it has created a thing called a "window id" in addition to a
"view id". This might be aimed at better support for exactly this sort
of problem. Of course that spec isn't finalised yet (nor implemented).

Andrew robinson wrote:
> What is your state saving method? You probably have your state saved to
> the server, it will only remember the state from the last post, and
> therefore you will not be able to post from past pages. Best thing to do
> is set your state saving method to client.
>
> -Andrew
>
> On 10/9/05, *Dave* <[EMAIL PROTECTED] > wrote:
>
> Hello,
> I have a problem with JSF which seems to be a JSF flaw. Any idea is
> appreciated.
>
> suppose I ha ve JSF page A, when user click a link in page A, a page
> B is opened in a new window. At this moment, the server side JSF
> view root is page B. If user click submit button in page A, all form
> data(not submitted yet) will be lost in page A because JSF think it
> is an initial request and goes to render phase immediately(no model
> update). From user's view, it is a post back to submit data.
>
> Popping up a new window is very common . Any idea to solve this
> problem? or It is JSF, no way. Thanks!
>
> Dave
>
>
>
>
>
> ------------------------------------------------------------------------
> Yahoo! Music Unlimited - Access over 1 million songs. Try it free.
>
>
>
>

---

Yahoo! Music Unlimited - Access over 1 million songs. Try it free.