You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by Ganesh <ga...@j4fry.org> on 2009/05/06 21:37:06 UTC
JSF 2.0 + javax.faces.ViewState
Hi Roger,
With the last minute changes I think an error has leaked in. It now
states that the javax.faces.ViewState is only to be replaced within the
submitting form. Imho all forms viewstates absolutely need to be replaced.
Below I'm citing the new spec jsdoc text on this subject for the rest of
the list to understand what we are about.
Best regards,
Ganesh
* If an update element is found in the response with the identifier
javax.faces.ViewState:
<update id="javax.faces.ViewState">
<![CDATA[...]]>
</update>
locate and update the submitting form's javax.faces.ViewState
value with the CDATA contents from the response.
Re: JSF 2.0 + javax.faces.ViewState
Posted by Werner Punz <we...@gmail.com>.
Ok Roger thanks for the clarification on this issue.
I also did not have portlets in my mind when I was asking
myself why this had been changed!
Obviously the Es in the EG are more E than I am an E,
so ashes to my head ;-)
That also makes things a slightly bit faster because you do not have
to walk over all forms doing the field update!
Werner
Ganesh schrieb:
> Hi Roger,
>
> I'm impressed - the "E" in "EG" obviously makes sense. Yes, it's true,
> portlets must be considered.
>
> If someone bothers to use a multi form approach within a servlet
> container and he wants to update the viewstates of other forms he may
> well explicitly elect them for rerendering.
>
> Best Regards,
> Ganesh
>
> Roger Kitain schrieb:
>> Hi Ganesh,
>>
>> I met with the Ajax EG team members about this and we decided to go
>> the route of updating
>> the submitting form, because in a portlet environment, each form may
>> have its own view/viewstate
>> that is different - in which case we would clobber that. Impls must
>> update the submitting form (at least),
>> and we lieave it (for now) as an impl detail if they want to update
>> all forms with
>> javax.faces.ViewState (since that is not specified). We have not
>> handled all portlet related cases
>> in the spec - that I am sure of.. I think if need be we can address
>> this in an MR.
>>
>> -roger
>> Ganesh wrote:
>>> Hi Roger,
>>>
>>> With the last minute changes I think an error has leaked in. It now
>>> states that the javax.faces.ViewState is only to be replaced within
>>> the submitting form. Imho all forms viewstates absolutely need to be
>>> replaced.
>>>
>>> Below I'm citing the new spec jsdoc text on this subject for the rest
>>> of the list to understand what we are about.
>>>
>>> Best regards,
>>> Ganesh
>>>
>>> * If an update element is found in the response with the
>>> identifier javax.faces.ViewState:
>>>
>>> <update id="javax.faces.ViewState">
>>> <![CDATA[...]]>
>>> </update>
>>>
>>> locate and update the submitting form's javax.faces.ViewState
>>> value with the CDATA contents from the response.
>>>
>>
>
Re: JSF 2.0 + javax.faces.ViewState
Posted by Ganesh <ga...@j4fry.org>.
Hi Roger,
I'm impressed - the "E" in "EG" obviously makes sense. Yes, it's true,
portlets must be considered.
If someone bothers to use a multi form approach within a servlet
container and he wants to update the viewstates of other forms he may
well explicitly elect them for rerendering.
Best Regards,
Ganesh
Roger Kitain schrieb:
> Hi Ganesh,
>
> I met with the Ajax EG team members about this and we decided to go
> the route of updating
> the submitting form, because in a portlet environment, each form may
> have its own view/viewstate
> that is different - in which case we would clobber that. Impls must
> update the submitting form (at least),
> and we lieave it (for now) as an impl detail if they want to update
> all forms with
> javax.faces.ViewState (since that is not specified). We have not
> handled all portlet related cases
> in the spec - that I am sure of.. I think if need be we can address
> this in an MR.
>
> -roger
> Ganesh wrote:
>> Hi Roger,
>>
>> With the last minute changes I think an error has leaked in. It now
>> states that the javax.faces.ViewState is only to be replaced within
>> the submitting form. Imho all forms viewstates absolutely need to be
>> replaced.
>>
>> Below I'm citing the new spec jsdoc text on this subject for the rest
>> of the list to understand what we are about.
>>
>> Best regards,
>> Ganesh
>>
>> * If an update element is found in the response with the
>> identifier javax.faces.ViewState:
>>
>> <update id="javax.faces.ViewState">
>> <![CDATA[...]]>
>> </update>
>>
>> locate and update the submitting form's javax.faces.ViewState
>> value with the CDATA contents from the response.
>>
>
Re: JSF 2.0 + javax.faces.ViewState
Posted by Roger Kitain <Ro...@Sun.COM>.
Hi Ganesh,
I met with the Ajax EG team members about this and we decided to go the
route of updating
the submitting form, because in a portlet environment, each form may
have its own view/viewstate
that is different - in which case we would clobber that. Impls must
update the submitting form (at least),
and we lieave it (for now) as an impl detail if they want to update all
forms with
javax.faces.ViewState (since that is not specified). We have not
handled all portlet related cases
in the spec - that I am sure of.. I think if need be we can address
this in an MR.
-roger
Ganesh wrote:
> Hi Roger,
>
> With the last minute changes I think an error has leaked in. It now
> states that the javax.faces.ViewState is only to be replaced within
> the submitting form. Imho all forms viewstates absolutely need to be
> replaced.
>
> Below I'm citing the new spec jsdoc text on this subject for the rest
> of the list to understand what we are about.
>
> Best regards,
> Ganesh
>
> * If an update element is found in the response with the identifier
> javax.faces.ViewState:
>
> <update id="javax.faces.ViewState">
> <![CDATA[...]]>
> </update>
>
> locate and update the submitting form's javax.faces.ViewState
> value with the CDATA contents from the response.
>