I just looked at the dialog example. Since it is demonstrating the use
of a return listener, the binding to the UIXInput is needed. In my
previous email, I was trying to say that in most cases, using a
component binding isn't necessary - the component can be retrieved
programmatically or use of the value attribute is sufficient.
-R
Richard Yee wrote:
Binding a component is usually unnecessary. You probably could
accomplish what you want to do with an el expression for your value
attribute. That would write the inputText value to a String attribute
in your backing bean. If you used a converter, you could have the
value written to a primitive or a numeric wrapper class.
-R
hns wrote:
hi
it is solved,i made one silly mistake in it,
at first i have write this
<tr:inputText label="Pick a number:" value="(Empty)"
partialTriggers="buttonId" />
i forget to write binding="#{launchDialog.input}" in it
thanks
