This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
I don't follow you. Apparently you're mistaking a 2-dimensional tabular display for executable code. All a dataTable (extended or not) does, is render the data based on its underlying model. It does not necessarily execute a loop to do so and even when it does, it's an internal "black-box" process that you can't tie into.
If you want the rows of the table to reflect some sort of specific information, you have to adjust the table's dataModel accordingly.
An IDE is no substitute for an Intelligent Developer.
Joined: Jun 19, 2011
Tim, thank you very much for reply
Actually, my data is based on underlying model, but there is also additional information which should be computed dynamically for each "log" var (this is necessary for heterogenous entities). I got it worked handling List.get method, but this is not what I expected to get, is there any more suitable solution?
One of the top 10 errors that people make when working with JSF is in thinking that a table dataModel must be an actual basic object such as an ORM Domain Model.
If the data doesn't fit your needs, just make a façade that does. Define a row class that either extends or aggregates the lower-level row-level object and make a collection of those façade row objects to be the wrapped data for the dataModel.
Joined: Jun 19, 2011
Tim, I agree with you, but i my case source code and jsf pages are autogenerated, and it is difficult to extend system to add this facade. I found workaround using List.get overridden method, it works for me,
Thank you very much for your help
One of the problems with these "A monkey can do it in 10 minutes" code generators is that almost every project sooner or later ends up with something that the generator can't handle, and the cost of working around the generator's limits can really bite into the benefits.
Technically, you are using a façade, but it's hard-wired into your custom list element accessor. Not ideologically pure, perhaps, but like I said, working around a limited framework generally requires ugly solutions.