[
https://issues.apache.org/jira/browse/CAMEL-10908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomohisa Igarashi updated CAMEL-10908:
--------------------------------------
Description:
Instead of carrying around the INPUT_TYPE/OUTPUT_TYPE exchange properties, let
Message hold the DataType directly as those exchange properties get out of sync
when Pipeline copies the message between IN and OUT.
{code:java}
public interface DataTypeAware {
void setDataType(DataType type);
DataType getDataType();
setBody(Object body, DataType type);
}
{code}
was:Instead of carrying around the INPUT_TYPE/OUTPUT_TYPE exchange
properties, let Message hold the DataType directly as those exchange properties
get out of sync when Pipeline copies the message between IN and OUT.
> Introduce DataTypeAware interface and let MessageSupport implement it
> ---------------------------------------------------------------------
>
> Key: CAMEL-10908
> URL: https://issues.apache.org/jira/browse/CAMEL-10908
> Project: Camel
> Issue Type: Task
> Components: camel-core
> Affects Versions: 2.19.0
> Reporter: Tomohisa Igarashi
> Assignee: Tomohisa Igarashi
> Fix For: 2.19.0
>
>
> Instead of carrying around the INPUT_TYPE/OUTPUT_TYPE exchange properties,
> let Message hold the DataType directly as those exchange properties get out
> of sync when Pipeline copies the message between IN and OUT.
> {code:java}
> public interface DataTypeAware {
> void setDataType(DataType type);
>
> DataType getDataType();
>
> setBody(Object body, DataType type);
>
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
