[jira] [Commented] (CAMEL-10908) Introduce DataTypeAware interface and let MessageSupport implement it

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CAMEL-10908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15889498#comment-15889498 ] 

ASF GitHub Bot commented on CAMEL-10908:
----------------------------------------

GitHub user igarashitm opened a pull request:

    https://github.com/apache/camel/pull/1497

    CAMEL-10908 Introduce DataTypeAware interface and let MessageSupport …

    …implement it
    
    This also solves CAMEL-10890
    
    This is a follow up of the discussion here:
    https://github.com/apache/camel/pull/1492
    
    Instead of carrying around the INPUT_TYPE/OUTPUT_TYPE exchange properties, introduced DataTypeAware which allows camel Message to store its DataType.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/igarashitm/camel CAMEL-10908

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/camel/pull/1497.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1497
    
----
commit 0366bc15c8ab8e6229246203c1fa4723c0f5a251
Author: Tomohisa Igarashi <tm...@gmail.com>
Date:   2017-03-01T00:06:41Z

    CAMEL-10908 Introduce DataTypeAware interface and let MessageSupport implement it
    
    This also solves CAMEL-10890

----


> 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)