[trinidad] how many view states are needed for dialogs?

[Daniel Niklas <co...@dniklas.de>]

Hi,

i'm using server side state saving (environment is a portal). How many view
states do i need when using 
the dialog framework of trinidad?

I want to reduce the number of view states in server
(org.apache.myfaces.NUMBER_OF_VIEWS_IN_SESSION), because of memory
consumption. 

Thanks in advance
Daniel :-)
-- 
View this message in context: http://www.nabble.com/-trinidad--how-many-view-states-are-needed-for-dialogs--tp19331773p19331773.html
Sent from the MyFaces - Users mailing list archive at Nabble.com.

Re: [trinidad] how many view states are needed for dialogs?

[Daniel Niklas <co...@dniklas.de>]

I made some observations, my example looks like this:

<tr:commandLink text="show dialog" action="dialog:my-dialog"
				windowWidth="600" windowHeight="300"
                                partialSubmit="true" useWindow="true"
				actionListener="#{myBean.myActionListener}" />

The commandButton which closes the dialog this one (no ppr here?!):

<tr:commandButton text="OK" actionListener="#{myDialogBean.close}" />

This szenario needs three view states (on the server). RestoreView is called
three times, that fits together?!
The dialog is rendered in an iframe, so two view states are needed: one for
the "normal" page and one for the dialog. But where comes the third view
state into the play?

best regards
Daniel
-- 
View this message in context: http://www.nabble.com/-trinidad--how-many-view-states-are-needed-for-dialogs--tp19331773p19371838.html
Sent from the MyFaces - Users mailing list archive at Nabble.com.