>System.out.println(fourth != first); // true
>>>>>
>>>>> If interested, looking into the different implementations of Camel’s
>>>>> DataFormatResolver should clarify this to you, specially the
>>>>> DefaultDataFormatResolver one.
>
DataFormatResolver one.
>>>>
>>>> Babak
>>>>
>>>> sohrab wrote
>>>> I was just looking through the latest code for
>>>> org.apache.camel.model.rest.RestBindingDefinition and I am not quite sure
>>>> how this works so
gt;>> Babak
>>>
>>> sohrab wrote
>>> I was just looking through the latest code for
>>> org.apache.camel.model.rest.RestBindingDefinition and I am not quite sure
>>> how this works so I'd appreciate if someone can explain it to me.
>&
at(name);
>> DataFormat outJson = context.resolveDataFormat(name);
>>
>> And further down, it sets the properties for "json" and then "outJson".
>> Now
>> I am wondering if that name resolves to the same DataFormat object
>> (especiall
ame DataFormat object
> (especially when you have RestConfiguration.jsonDataFormat set), what stops
> setting "outJson" properties, such as unmarshalType, not overriding the
> properties we just set for "json"?
>
>
>
>
&g
mat set), what
> stops setting "outJson" properties, such as unmarshalType, not overriding
> the properties we just set for "json"?
--
View this message in context:
http://camel.465427.n5.nabble.com/RestBindingProcessor-JSON-Data-Format-Config-tp5757103p5757186.html
Sent from the Camel - Users mailing list archive at Nabble.com.
taFormat set), what stops
setting "outJson" properties, such as unmarshalType, not overriding the
properties we just set for "json"?
--
View this message in context:
http://camel.465427.n5.nabble.com/RestBindingProcessor-JSON-Data-Format-Config-tp5757103.html
Sent from the Camel - Users mailing list archive at Nabble.com.
