defaultSerializationFormat property has no effect after upgrade to 2.0.0
See original GitHub issueAfter an upgrade of an application from Camunda Spring Boot Starter 1.3.0 to 2.0.0 (each with Camunda 7.6.0) I noticed that the setting of the default serialization format via
camunda.bpm.defaultSerializationFormat=application/json
has no effect anymore. The serialization format is always application/x-java-serialized-object.
I noticed that there is a unit test that covers this setting which passes. But in the end it does not work. I tried to find out what the problem is, but I did not manage to.
I probably can offer some kind of repro if that helps. But maybe the cause is obvious for you; in that case - I guess - the repo is not needed.
Issue Analytics
- State:
- Created 7 years ago
- Comments:11 (10 by maintainers)
Top Results From Across the Web
Spring Boot and Spin Json serialization - Jackson annotations ...
Issue: defaultSerializationFormat property has no effect after upgrade to 2.0.0. opened by FrVaBe on 2016-12-15. closed by jangalinski on 2017- ...
Read more >CHANGELOG.asciidoc - tinkerpop - Git at Google
* Fixed problem with Gremlin Server sometimes returning an additional message after a failure. * Allowed spaces in classpath for `gremlin-server.bat`. * ...
Read more >Add defaultSerializationFormat to References and Installation ...
There is no information WHERE to set this property. So people are lost. we need to show how to set it in bpm-platform.xml...
Read more >MediaWiki 1.36.0 - Installatron
It has been enabled by default since MediaWiki 1.27. ... Updated wikimedia/cldr-plural-rule-parser from 1.0.0 to 2.0.0.
Read more >Celery Documentation - Read the Docs
If this is None no rate limit is in effect. If it is an integer, it is interpreted as “tasks per second”. The...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I created a repro for this bug in my camunda/camunda-external-task-demo/ repository. Although I created this repository to do some investigantions on external task usage it contains a unit test that checks the serialization format. Use the CSBS-Issue-185-repro tag to check out the version that just basically handles the issue.
The configuration to use the JSON serialization was done in the
application.properties
file. The code is camunda spring boot starter version 1.3.0 / 2.0.0 compatible.The test
DefaultSerializationFormatTest.checkDefaultSerializationFormatHandling
will fail with the Camunda Spring Boot Starter 2.0.0 version on the classpath (current dependency configuration). If Camunda Spring Boot Starter 1.3.0 is used instead, the test will pass (change the dependencies in the pom.xml).I guess, this can be closed then …