I have the same problem.
comboBox component from the beggining designed as input with client side suggestions (light version of suggestionBox) not as select component. So in order to use objects instead of just strings you should use converters.
Thank you very much for the reply.
Fundamentally, when we display values to users, we need to do the translation and display to the users. When the user selects one from the client side suggestions, it cannot be used as such since itâ€™s a translated value and we need to use the actual value in any of the operation.
As you mentioned, one has to use converters, but if I use converters, then I need to maintain a sort of Map with the translation to the actual object. When the user picks or selects one value in the combo, then based on the user selection(translated value), I need to get the Object. We need to have as many maps in as many places where we use Combo box. This I think will not be an elegant solution
PL correct me if I am missing something
Can you please let me know whether this request can be taken up.
we have the same problem! why they didn't make a NORMAL html select??? Are there other solutions than using converters? Or we are stick with using h:selectOneMenu???
I could tell you the same one more time. Combo Box was designed as suggestions able Input. It isn't a select. So we can't aggree that lost feature present there
too bad...I thought I could use to have a css customizable select (as I can't customize standard selects, do you know a way?)...
Selecting just text reduces a lot the using possibilities of this component...
check our standart components skinning article. Unfortunatelly now it doesn't covers all the functionality currently added but will be usefull fro you working with selects:
I understand that the rich:comboBox works as designed. So, I want to look into making a variation that supports both values and labels.
Before I go down that path, are there any known limitations that would make this difficult?
I see how the rich:comboBox works now and I have it working well enough, but I'm curious why it was implemented as an input instead of a select.
Can someone name an example or two where it is useful in this way? The component demo only uses it in a select type of context so I'm having trouble seeing the benefits of it being designed that way.
client-side autocompletion case.
God bless you.