Hello Federico, I absolutely agree with your proposal. Thanks for your feedback. It makes more sense than an additional batch component.
I looked a the code, based on your proposal, even without the optional aggregationStrategy, I think I would need to - develop a new batch EndpointMessageListener - develop a new batch SimpleMessageListenerContainer - update the SjmsEndpoint which creates the consumer I was wondering if at I should limit batch to an InOnly exchange? Adding an optional aggregationStrategy eg to only add the message body cast to a custom class to a list would be useful. After looking at the code again, I was wondering if I could simply develop listener and container that do not automatically commit or rollback at the end of the unitOfWork. Then I could consume each message in a regular aggregationStrategy and commit when the aggregationStrategy is completed and the result processed. I do not currently have write access to the Apache Camel Jira. Regardless, let me see what I can put together, and if I am confident in the result, then I can consider a proper submission. I will save my „updated“ SJMS component in my GitHub repo. Best Regards, Marcus
