Skip to content
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

Make charset configurable in JdbcExecutionContextDao #795

Closed
spring-projects-issues opened this issue Apr 5, 2019 · 1 comment
Closed

Comments

@spring-projects-issues
Copy link
Collaborator

Matthias Fiebiger opened BATCH-2804 and commented

This is a known issue. With Spring Batch 4 it has got worsened.

With Spring 4 The XStreamExecutionContextStringSerializer is deprecated. You should use the Jackson2ExecutionContextStringSerializer. But this Serializer can only be used with utf-encoding. JdbcExecutionContextDao only works with ISO-8859-1. Thus, by default all spring Batch 4 applications will destroy special characters. Some Databases do not except the broken characters.


Affects: 4.1.1

Reference URL: https://jira.spring.io/browse/BATCH-2057

Attachments:

@fmbenhassine
Copy link
Contributor

The default encoding in JdbcExecutionContextDao has been changed to UTF-8 (see #3983), which should fix this issue.

Moreover, the charset has been made configurable in JdbcExecutionContextDao (see 9315a3b).

@fmbenhassine fmbenhassine modified the milestones: 5.0.0, 5.0.0-M3 May 17, 2022
@fmbenhassine fmbenhassine changed the title "ISO-8859-1" charset usage is still forced in JdbcExecutionContextDao [BATCH-2804] "ISO-8859-1" charset usage is still forced in JdbcExecutionContextDao May 17, 2022
@fmbenhassine fmbenhassine changed the title "ISO-8859-1" charset usage is still forced in JdbcExecutionContextDao Make charset configurable in JdbcExecutionContextDao May 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants