I want to accomplish the following:Application receives a bunch of parameters as a POST requestApplication launches Spring Batch job with the same parametersSpring Batch runs the job based on the parameters.However, string parameters passed to a Spring Batch job cannot exceed 250 characters, which makes it impossible to do this the simplest way (some of the parameters can be arbitrarily long): copying the parameters from the POST request into a map and building a JobParameters object from this map which is then passed into jobLauncher.run to run the job.Is this limitation intentionally there in order to discourage users from trying to use JobParameters for this purpose? I've considered creating a separate table in the Spring Batch database to hold the parameters instead of using JobParameters (writing to the table before launching the job and then reading from it from inside the job), but I have to wonder if the fact that JobParameters has this limitation in the first place means that I'm not supposed to use Spring Batch this way.Is my thinking right, or is the 250 character limit in JobParameters perfectly arbitrary? Is there a better way to accomplish this than using a separate table to store the parameters?
Idiomatic way to pass long strings as parameters to Spring Batch
java;spring