Kevin Urban

Hi Scott, I feel you, the anti free time conspiracies hit hard sometimes ;) But as I said, I found a workaround so absolutely no pressure from my side. I'm just reporting this behavior as a very small contribution. You are right though - we first actually found this behavior when our App crashed with out of memory. As always, while developing, I only tested with several dozens of rows, and our testers actually found the problem when testing with several hundred / few thousand entries. That led me...

Hi @sconway, Thanks for your reply. From my POV it's not urgent, and I appreciate your input. Also, I'll be the first to admit that the concrete use case I was building is a hacky temporary solution that primarily is implemented this way because of time constraints and will hopefully be replaced soon. Nonetheless I was confused by the fact that StatefulBeanToCsv.write(Stream) consumed the whole stream before starting to write to the Writer and felt it was worth to point out. To answer your points...

StatefulBeanToCsv.write(Stream) processes complete Stream before writing to writer