Support camel dataformat configuration for marshaller/unmarshaller #816

[luigidemasi]

this pr allow the configuration of a dataformat directly in properties file, something like:

camel.source.unmarshal=fhirJson
camel.source.unmarshal.fhirJson.fhirVersion=R4
camel.source.unmarshal.fhirJson.prettyPrint=true

[oscerd]

Looks good to me. Thanks a lot. @valdar cc

[oscerd]

Can you fix the codestyle?

[valdar]

I hope this switch case could be avoided by something on the line of context.createDataFormat(dataFormatName)

[valdar]

I was under the general impression that this usecase should have worked already using something like:

camel.dataformat.fhirJson.fhirVersion=R4
camel.dataformat.fhirJson.prettyPrint=true

see https://github.com/apache/camel-kafka-connector/blob/master/core/src/test/java/org/apache/camel/kafkaconnector/DataFormatTest.java#L128
Give me some more time to investigate further.

[luigidemasi]

I was under the general impression that this usecase should have worked already using something like:

camel.dataformat.fhirJson.fhirVersion=R4
camel.dataformat.fhirJson.prettyPrint=true

see https://github.com/apache/camel-kafka-connector/blob/master/core/src/test/java/org/apache/camel/kafkaconnector/DataFormatTest.java#L128
Give me some more time to investigate further.

It should work but it doesn't, if you look at the test, you disable validation and then assert that the validation is enabled.
I think it's a bug on camel-main atuoconfiguration that doesn't bind the dataformat in the registry after configuring it and an empty new one is created when the route starts. Opened an issue for this: CAMEL-16032

[valdar]

Thanks a lot for the effort in seeking the root cause of this and fixing it @luigidemasi !
I close this and the effort is tracked here: #816