Shekar Chandu wrote:5. How come JSF know the view with out submitting a first request by user
As I previously said, there is no View, and therefore no View State until a request has been made. The JSF will also instantiate any missing Model objects (and therefore Model State) when the request is made, so both are in sync when the web page is first displayed.
Shekar Chandu wrote:4. with out submitting a single request to server how can they be differernt?
JSF is like Enterprise JavaBeans in that things have both active and inactive forms. A webapp, unlike a regular application, is not a continously-running program. A webapp is only "running" when it is processing a user request. And since requests are based off threads in the server's thread pool, that means that at any given time, a webapp may have 100 instances "running" (for 100 different users), or 0 instances running. Each instance has its own unique state data (user session), and that includes both the JSF infrastructure (including View Component Tree) and the JSF Model objects. But once the request has processed and the response has been sent, the webapp reverts to an inactive state (from that user's point of view) until another request is made by that user (if ever).
Shekar Chandu wrote:3. what does inactive form mean?
Shekar Chandu wrote:2. But below statement again relates View State to the strucutre of page that gets created as Tree object and stored in session