Hi Jeff,
while you are correct in asking about the sense of the code if no value
attribute is specified,
you are incorrect in saying, that the value attribute is required.
The only thing which is required is the
onchange="Tobago.submitAction('combo1');"
attribute.
The code works fine whether or not you specify the value attribute.
The reason why I don't have a backing bean is, that I do want to generate the
component tree on
the fly, i.e. without knowing in advance which components will actually be
displayed. In such a
use case I am unable to create a backing bean with getters/setters since that
would mean to create
a Java Source and compile it at run-time of the jsp.
Thanks to everyone for getting this to work.
Regards,
Peter
Jeff wrote:
> The valueChangeListener can not fire from your code.
>
> >> <tc:selectOneChoice
> >> valueChangeListener="#{mybean.processValueChange}"
> >> onchange="submit();" value="">
> >> <f:selectItems value="#{mybean.featureValue_1}" />
> >> </tc:selectOneChoice>
>
> Look, you have hard-coded the value! So how can the value ever change?
>
> And your original example code didn't even have a value attribute defined!
>
> Notice it's called *value*ChangeListener, not selectionChangeListener. :)
>
> Make the selectOneChoice's "value" attribute a value-binding expression
> that references a String property on some backing-bean. When you select
> something in the combo box, it will call the setter for that property,
> using the itemValue from the selectItem. It should also fire a
> valueChange event.
>
> Hope this helps.
>
> Regards,
>
> Jeff Bischoff
> Kenneth L Kurz & Associates, Inc.
>
--
Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen!
Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer
