rich:comboBox vs. h:selectOneMenu

[daxxy]

I have these two components with identical list contents using s:selectItems component. Like this

<h:selectOneMenu value="#{office.state}">
 <s:selectItems value="#{statesList.resultList}" var="_state"
 label="#{_state.abbreviation} (#{_state.fullName})"
 itemValue="#{_state.abbreviation}" />
</h:selectOneMenu>

and this

<rich:comboBox defaultLabel="Start typing or click the arrow" value="#{office.state}">
 <s:selectItems value="#{statesList.resultList}" var="_state"
 label="#{_state.abbreviation} (#{_state.fullName})"
 itemValue="#{_state.abbreviation}" />
</rich:comboBox>

The JSF selectOneMenu renders a list of options that look like this

AL (Alabama)
AK (Alaska)

where the Richfaces option list looks like this

AL
AK

Why the difference?

TDR

[netdrag]

I am not sure, but I think I found some posts where someone explained that the combobox ignores the label attribute of s:selectItems and this is an expected behaviour.

[ilya_shaikovsky]

yes, because combobox is input with client side suggestions, not a select.

[daxxy]

Ah, thank you, that makes sense!

Does richfaces provide a select? I hesitate to ask this since it probably reveals a deep misunderstanding of richfaces, but I'm doing it anyway.

Still just a newbie, but a curious one,

TDR

[ilya_shaikovsky]

inplaceSelect is closer one to standard.

ListShuttle and pickList - rich selectMany components but seems not for your case :).

[daxxy]

rich:inplaceSelect seems to work, but my users also want to be able to enter strings of their own devising and it seems that inplaceSelect doesn't allow this.

Maybe I'll have to put an additional input field (e.g. inplaceInput) to accomodate this request.

thanks for the info, Ilya!
TDR