The javax.faces.STATE_SAVING_METHOD context-param in web.xml was a
duplicate. Visual Web Pack put a ton of settings on one line including
this one, set to server. Once I removed my dupe context-param and set
the first one to client, the weird unexplainable behaviors went away.
So I would say yes Woodstock does require client side state saving for
some things to work properly.
Ryan
Ryan de Laplante wrote:
> I'm still having "fun" getting my real application to work like my
> test app. It mostly works, but I find value change events firing
> multiple times first showing a null new value (correct) followed by
> the previous value being re-set. I also see the value change events
> not firing in the same order as the test app.
>
> I'm thinking this has something to do with view state. The test app
> shows a very long encoded view state in HTML output and AJAX requests,
> but the real app shows what appears to be a server side view state token:
>
> <input type="hidden" name="javax.faces.ViewState"
> id="javax.faces.ViewState" value="j_id7:j_id8" />
>
> I have added the following to my web.xml, and even restarted the app
> server, but it doesn't make a difference. I can't get it to output an
> encoded view state. Hopefully once I can figure that out, my app will
> finally work properly:
>
> <context-param>
> <param-name>javax.faces.STATE_SAVING_METHOD</param-name>
> <param-value>client</param-value>
> </context-param>
>
>
> Thanks,
> Ryan
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_woodstock.dev.java.net
> For additional commands, e-mail: users-help_at_woodstock.dev.java.net
>
>