Your solution will break your system if the table you export has many rows (e.g. >1000) as all rows are read into memory.
It sounds strange that you don't get any result of you apply a view criteria to your vo. Have you executed the query before trying to export the result?
Can you post the code used for the export?
<af:exportCollectionActionListener type="excelHTML" exportedId="foodTable"
I just use the component.
Have you executed the query before trying to export the result?
Yes, i have a another button that applies the view criteria.
I don't think that there will be a problem with >1000 because i don't render the tables.. Or it doesn't matter?
The memory conception is not dependant on rendering the table, the memory is used reading the data from the table into memory. Seeing the fetch size to -1 will read all dies into memory at once, disabling all caving or other memory techniques.
You may want to check some sample https://pinboard.in/search/u:OracleADF/?query=export
I tried close to everything that you gave me.
I will try to explain again, as good as i can.
two tables on the page (render = false) T1 and T2
two buttons with exportCollectionActionListener in them B1 and B2
and another button that adds applies view criteria to the view objects. B3
If i don't click on B3 the other components work ok.
If i don't click on B1 or B2, and click on B3.. the export works just the first time.
I simply don't get why it doesn't work.