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'm afraid that your example is so long that I can't read it. However, in all the years I've worked with JSF, there's only been one app I've written that built up a dataTable in Java code, and that one is a generic table editing app when the columns vary depending on which table is being edited. It's far, far, easier to code XML in the View as long as the table format is static.
In any event, JSF does not "submit a datatable". What actually happens is that the input controls within the dataTable display are scanned when you fire a command, and their values are sent to the FacesServlet, from whence they go through the JSF controllers and are posted to the DataModel that backs the dataTable. In other words, the rows in the wrapped data of the DataModel are directly updated by the controllers with the data control values from the submitted form. This is true whether you use the XML definitions or do brute-force creation of the UIComponent subtree in raw Java code.
The caveat on this is that since the backing data rows are updated, they cannot come from a read-only data source. In other words, you can't use a jdbcDataModel; you must use something such as a List- or ArrayDataModel.
Customer surveys are for companies who didn't pay proper attention to begin with.