Instead of having this dumb container-only class, the 'massaging logic' should be moved here instead since it definitely does not belong in the controller. This could be done with a lazy calculation pattern here (probably the easisest). Another option is to leave this class as is and move the massaging logic to a job-scoped `FactoryBean` that would instantiate this.

It would also be easier to unit-test the massaging logic in those circumstances.