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.
WHY are you not allowed to use dataTable? If this is some idiot manager's idea, its' THEY who need some head-banging!
Nested datatables are painful, though. Even in the latest versions of JSF, getting the current row of the inner table requires some awkward code.
Customer surveys are for companies who didn't pay proper attention to begin with.
Joined: Apr 10, 2014
There is some requirements for not using datatable.. If anyone can tell me how to pass values from backing bean for each column.. I guess i need little example. I am somewhat successful in building a raw table and one nested table. But unable to pass values :(
"some requirements" is often a euphemism for "manager is an idiot". My recommendation on how to solve such problems involves updating one's CV if said manager(s) cannot be persuaded to discard such arbitrary limitations. Deliberately avoiding industry standard solutions because some "expert" arbitrarily forbade them just means that whatever workaround is done is typically going to be time-consuming, expensive, often fragile, and more difficult/expensive to maintain.
JSF expects to do all the fetching and updating between Model and View itself. JSF is a fairly pure implementation of the MVC paradigm, but in JSF, you don't write Controllers to do the transfer of data between Model and View, they are pre-written parts of the JSF FacesServlet and tag implementations. And the h:dataTable tag implementation in particular for such cases as the one you describe.
Unfortunately, the current implementation of dataTable doesn't take nesting into account, so some helper code has to be written that makes up for that lack.