[
https://issues.apache.org/jira/browse/CAMEL-17814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-17814.
---------------------------------
Resolution: Won't Fix
Its due to how data-formats are modelled in Camel, that means camel-core-model
dictates which options we have.
The gson have some very special options that are only available for gson, which
the other json data formats do not have. So the model has a common
middle-ground.
Today we should have made each data format indepdendt and not associated with
the same base json dataformat. But that is how this was created many years ago.
> camel-gson - Dataformat documentation doesn't cover all possible options
> ------------------------------------------------------------------------
>
> Key: CAMEL-17814
> URL: https://issues.apache.org/jira/browse/CAMEL-17814
> Project: Camel
> Issue Type: Task
> Components: camel-gson
> Affects Versions: 3.15.0
> Reporter: Martin Muzikar
> Priority: Minor
> Fix For: 3.18.0
>
>
> When looking at [documentation for
> camel-gson|https://camel.apache.org/components/3.15.x/dataformats/gson-dataformat.html]
> it looks like the only use cases are marshalling and unmarshalling into a
> specific type. Whereas there are some use cases not covered in the doc in the
> [GsonDataFormat|https://www.javadoc.io/doc/org.apache.camel/camel-gson/latest/org/apache/camel/component/gson/GsonDataFormat.html].
> It might be helpful to add a link to javadocs for dataformat components since
> it looks like there's always more options in the DataFormat class.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
