All,
I've got a bug that one of our testers found where we behave differently
from the RI. Let me lay out the situation and the two options I have
come up with for solutions. This applies to at least the 1.2.x and
2.0.x releases.
The application has a simple logout.jsp that we get to via a
Hi Mike,
2) do something in the form renderer to indicate that the state needs to be
saved, maybe setting a request attribute that can be checked in saveView to
determine whether to actually save state or just return null.
I would lean towards option 2 - I don´t see how the saved state would
What about ajax and http get which perse do not post a form in all cases
but can post data back into the lifecycle?
OK,http get is handled, but still there is ajax which can trigger
a post without a form.
Werner
Am 11.06.10 16:13, schrieb Martin Marinschek:
Hi Mike,
2) do something in
Hi
In theory, if there is no form there is no state saved, so the ajax received
will not have the state and no postback could be sent. Ok, if the view state
is saved in some different way by other alternate ajax component, the point
in common is that any component that writes the state should
Leo,
So I just did a little digging through the facelets code, and it looks
like in the facelets case, we already are doing something similar to
what you are proposing. ViewHandlerImpl's writeState method looks like
it only gets called by the encodeEnd on HtmlFormRendererBase. So I
think
