Skip to content

Revisit the default behaviour of job parameters conversion #3960

Closed
@fmbenhassine

Description

@fmbenhassine

The current behaviour of the DefaultJobParametersConverter has been confusing in many situations:

  • The way to specify parameter types with the parameter(type)=value notation is not friendly to command line arguments and environment variables
  • The way to specify identifying / non identifying job parameters with +/- prefixes is not friendly with Spring Boot

While it is possible to provide a custom JobParametersConverter and set it on the CommandLineJobRunner or JobOperator, I believe the default behaviour should be reviewed for a better getting started experience for batch users and a better integration with Spring Boot. Since this could be a breaking change, I see v5 as a good opportunity to revisit this part of the framework.

References:

Related issues:

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions