Thank you for the PR!

I am just wondering, have you tried to make StaxEventItemWriter extend AbstractFileItemWriter to inherit that state management / resources binding "feature"? StaxEventItemWriter currently extends AbstractItemStreamItemWriter. I am asking because to me writing to a file (be it flat, json or xml) is the same thing, and currently only FlatFileItemWriter and JsonFileItemWriter inherit from AbstractFileItemWriter, so probably it's a good time to see if StaxEventItemWriter can/should join the hierarchy as well.

Probably this is not possible (due to previous design considerations which I need to check), in which case we can proceed with this PR which looks good to me.

Thanks for the suggestion!

I did consider making StaxEventItemWriter extend AbstractFileItemWriter. However, my understanding is that the XML writing model in StaxEventItemWriter is quite different, and I’d need to spend more time reviewing AbstractFileItemWriter’s state/restart and open/close contract to see how well it would fit.

I initially tried to bring the implementations closer, but the changes quickly grew in scope. Given the potential side effects and compatibility concerns, I chose to keep this PR narrowly focused on fixing the immediate issue. 😅

Thank you for your feedback. That makes sense!

I will proceed with merging this PR for now and we can improve things if possible in a later iteration.

LGTM 👍 Rebased and merged as 5dc40a6.

Thanks again for looking into this and for contributing a fix!