Attached test case that shows this issue.

Steps:

• Load welcomeICEfaces.jsf
• Click on the Export button. The exported CSV will only contain the column headers.

Support case #11869

No modifications to the data exporter have been made since October 19.

Now, it seems like the InnerTableCSVExporter is always getting passed the first-row inner table to export, and thus it's not exporting anything.

A similar thing happens when any row other than the first one has no nested data. All the inner tables are printed correctly from the first row up to the row with no nested data, after that, all the subsequent rows do not export their inner tables.

While the client id of each inner table seems to be correct (i.e. they are different from each other), their state is not correct; calling table.getRowCount() returns 0 for all the inner tables (which have data) that appear after an inner table with no data.

This even happens when doing an entire visit tree procedure for each inner table. This is what gets printed when trying to find each inner table client id and calling getRowCount():

• iceForm:testTable:0:innerTestTable 2
• iceForm:testTable:1:innerTestTable 0
• iceForm:testTable:2:innerTestTable 0
• iceForm:testTable:3:innerTestTable 0

The third and fourth inner tables actually have 2 and 3 rows, respectively.

The problem starts with a change to DataTable.java (in the ACE folder) at revision 32831 for ICE-8798. I will see if the problem can be solved by adjusting the custom exporters to these changes or if the fix lies on the DataTable.java code.

Committed fix to the trunk at revision 32995.

The fix consists in resetting the data model of the inner table before the export process starts.

Committed improvement at revision 33062 to export inner table headers if they are defined inisde an ace:columnGroup and ace:row's. Added constructor to OuterTableCSVExporter to only require to pass the id of the inner table; this custom exporter will try to find the inner table component instance in this case and also in the case where the instance object is passed as well but it happens to be null.

Committed a fix at revision 33081 to support inner tables nested inside other containers when using the new approach to initialize the outer table exporter.

Updated showcase demo to use the new approach.

Verified this change (rev# 33095) in showcase -> DataExporter -> Custom Exporter, and found this behavior: even when no innerTable has been selected, the exported csv file contains the innerTable1 data in the exported file. Is this correct?

This JIRA cannot be verified using the attached war file, as there are errors when deploying it.

Yes, that behaviour is correct, since it's specified in the bean to use innerTable1 as the default inner table.

Testing for this feature should be done on the showcase, so no need to use the attached war.