> I bought JSF in Action but it only provides a simple "read-only" > dataTable example. I'm was having trouble grasping how the Collection > underlying the dataTable is updated based on the inputs from the UIInput > components but it sounds like JSF handles that. If that is the case when > does one need to use a component binding? There is an example in JSF in > Action that builds a dataTable that has an "Approve Project" commandLink > in one of the columns. In that case "Approve Project" is bound to an an > action method. In that action method they reference the UIData component > to determine which project was selected for approval. Is this the > typical use case for a dataTable with a component binding?
That's a good book but I haven't gotten very far with it yet. I will try and take a look at the example you are referring to when I get home tonight (the book is not here.) I'm still a little bit fuzzy on the component binding but I don't really see why you would need it in this example. I did a very simple example where I used command link and a listener. I used an <f:param> tag as well and in my listener I can pull that parameter out of the request. I think that is even simpler than the binding approach. Try that and let me know what you think. > Norm sean
