SiSi'mon schrieb:
I have read a lot on "component binding" but still do not understand under
the hood (in low level object/class terms) what it is. We do have some
beans that are session scoped.
A the component binding is basically the code representation of
the tag in the page you have bound to...
the binding itself is just an attribute which gets assigned the
component itself if set.
You then can use it on the code side to influence its behavior, which
child components you have etc... pretty much everything.
It really depends on your programmingmodel... most of the times you do
not do it because it is easier just to set the values, but a model like...
public String doMyAction() {
textField1.setValue("hello world");
//textField1 is a binding to a h:inputText component
return "done";
}
is possible, this looks very familiar like the programming model
approached by classical rich client ui frameworks where you alter
various aspects of the component on code level.
And this approach is used for instance by the Netbeans Visual Web
Plugin.
In the xhtml page that is failing, the word "binding" is never used. The
backing beans used in the page are request scoped but we do have a user
object that is session scoped which every page uses I believe.
such an object should be no problem... unless the user object has some
componen bindings in there....
It is kind of hard to nail down, can you post an error log maybe?
