I believe that you still should be able to use just table and not use bindings for that case. In similar case - I created set of facelts with different inputs which could be used and added them to columns using ui:include. The facelet to include was returned from backend according to type of the control required. And passing value binding and other parameters to facelet was done through ui:param.
Thanks so much for the response. I seem to be asking for a lot of help these days.
So the backing bean contained a UData object that represented the table. When rendering the table and iterating over the list of objects, you would perform a ui:include using a value that was contained in the current object? And the current object was passed to the included page via a UI:param?
I think I'm following the idea. When the page was submitted did the values get updated or did you update the values with ajax calls?
Is there any chance that you could provide a sample?
Thanks again for all the help. It's really great of you to give me all this assistance.
I started thinking about what you had suggested, using different pages to include based upon the data and I began implementing this solution. Everything seemed to work well until I tried to dynamically include the pages. It seems that the <ui:include> tag does not behave as I expected when including the pages dynamically in a loop. I played around with it a bit and it seems that the <ui:include> is processed prior to looping through my records. I don't know if this is the case but is there a solution that will accomplish what I am attempting? Or am I simply doing it incorrectly?
Thanks again for the help..