Skip to content

JdbcExecutionContextDao#afterPropertiesSet misses null ExecutionContextSerializer [BATCH-2779] #826

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
spring-projects-issues opened this issue Dec 10, 2018 · 0 comments
Labels
has: backports Legacy label from JIRA. Superseded by "for: backport-to-x.x.x" in: infrastructure type: bug
Milestone

Comments

@spring-projects-issues
Copy link
Collaborator

Michael Minella opened BATCH-2779 and commented

While normal creation of the JdbcExecutionContextDao is handled by the FactoryBean implementations for the JobRepository and JobExplorer, the call to afterPropertiesSet does not confirm that the object created is completely valid.  Specifically it does not validate that the ExecutionContextSerializer is not null.


Affects: 4.0.0, 3.0.9

Referenced from: pull request #673

Backported to: 4.1.1, 4.0.2, 3.0.10

@spring-projects-issues spring-projects-issues added type: bug has: backports Legacy label from JIRA. Superseded by "for: backport-to-x.x.x" in: infrastructure labels Dec 16, 2019
@spring-projects-issues spring-projects-issues added this to the 4.2.0 milestone Dec 16, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
has: backports Legacy label from JIRA. Superseded by "for: backport-to-x.x.x" in: infrastructure type: bug
Projects
None yet
Development

No branches or pull requests

1 participant