That's what I observed with my evaluation of RF4.x (migrating from RF3.3.3): it seems not possible to submit the contents (object or some attribute) of the iteratorvariable ("var") of the autocompletes inner table.

By using some javascript hacks (setting an invisible input value or a specific styleClass to the ID or UUID of my object / entity) I was able to retrieve the corresponding object / entity by looking it up again, but this was noch a very *nice* approach.

It's very time consuming, indeed. I've also spend almost two workdays search for a replacement for the rich:suggestionBox. Loading everything to the client (like 10k of articels or customers) is not an option.

Is there any chance that richfaces become usefull in the next ten years? The showcase suggerate a lot of thing that I wanted to do, but in reality nothing of this works. The examples in the showcases are trivial, because they are all about String. There no no usage of more complex objects, which would be the real use case. I am doomed with richfaces at this project, it is like flying to the moon with a paper plane. The customer says "I want this, and this and it have to look like this" and my answer is "Well, we can show up text. And buttons, great!". Application development like 50 years ago...