You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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
changed the title
"ISO-8859-1" charset usage is still forced in JdbcExecutionContextDao
Make charset configurable in JdbcExecutionContextDao
May 19, 2022
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:
The text was updated successfully, but these errors were encountered: