Thanks a lot. Your answer really eliminates some of my confusions about
JSF.
--
Wang Zeng
On 4/23/06, 王曾wang_zeng <[EMAIL PROTECTED]> wrote:
>
> Thank you, Craig.
> If we preserve the tree on the server, then the tree sholud be saved
> in
> session scope. If we don't save the tree on server, then everytime a
> request arrives, the tree should be reconstructed using the value
Thank you, Craig.
If we preserve the tree on the server, then the tree sholud be saved in
session scope. If we don't save the tree on server, then everytime a
request arrives, the tree should be reconstructed using the value of the
hidden field. Am I right?
On 4/23/06, 王曾wang_zeng <[EMAIL PROTECTED]> wrote:
>
> Graig,thank you for your answer.
> Acorrding to your answer, JSF component tree should be created everytime a
> request arrives. Will it be a waste of time.
> Asp.net use hidden-type input html tag to record the status of the
> component
> tree
Graig,thank you for your answer.
Acorrding to your answer, JSF component tree should be created everytime a
request arrives. Will it be a waste of time.
Asp.net use hidden-type input html tag to record the status of the component
tree. Dose JSF do it the same way?
On 4/23/06, 王曾wang_zeng <[EMAIL PROTECTED]> wrote:
>
>JSF provides us with a collection of standard UI components, and these
> components are integrated with JSP via JSF tag. when the JSP is executed,
> a
> tree of components will be constructed on the server. I wonder how many
> copies of this
JSF provides us with a collection of standard UI components, and these
components are integrated with JSP via JSF tag. when the JSP is executed, a
tree of components will be constructed on the server. I wonder how many
copies of this tree should be preserved on the server to remember the status
7 matches
Mail list logo
