Originally posted by Vishal K Patel:
what is binding doing internally?
How it will affect the normal life-cycle of JSF page?
where and when should I use it?
I have 5 JSF components in my page. On some action...I need to set some properties of those components from the backing bean.
now...if I am doing with the scope request and using binding...i can set all the properties of all the components of that page.
or...with session scope and without binding i can do the same.
which one is the better approach?
Is it good idea to keep all the states of all components stored in session??? or bindind could be the good alternative???
Originally posted by Sarathy Srinivas:
@ William.. there are many ways to reach the page. Your method would involve doing this for all the links to that page. this is something that, though possible, im looking to avoid. Is there a way to check the request parameter? If so what method should i use?
[ February 18, 2008: Message edited by: Sarathy Srinivas ]
Originally posted by Ben Souther:
What you're trying to do will give you nothing but headaches and will most likely result in a slow application.
Originally posted by lakshmi manepally:
I am getting thsi kind of error when I was doing build
Cannot find symbol class Content
Originally posted by Qussay Najjar:
You can use this:
it will work..