Yes, it will not works. And I believe that not native for the component, because it's just Input and not a Select based component. And I'm actually never liked of suggestionObjectsfeature in 3.3.x which partially solved that problem using custom JS saving. That's why in 4.x we designed rich:select. It supports the same direct input but works as a pure selectOne. It not supports multi-column mode for first version - but I prefer to think about rich:select extension rather than teaching Input to deal with objects selection again.
It's actually quite solving my problem indeed!
Didn't realize that this rich:select was available and was also "autocomplete-capable".
Thanks for your answer!
Can you tell me when (or in what release) this feature enhancement is planned for rich:select? Specifically, multi-column presentation and an ajax mode for retrieving the list of selectable objects.
rich:select is problematic if you have more than 1000 lines of data.
Try loading 100k lines into rich:select please. View will likely exceed 10MB...
It is possible though with some fiddling to make autocomplete control based on rich:autocomplete that will submit ID's. There is more info on forums if you search a bit.