You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Akitoshi Yoshida (JIRA)" <ji...@apache.org> on 2015/08/21 10:55:45 UTC

[jira] [Resolved] (CAMEL-9093) Provide an unparsed read mode for olingo2

     [ https://issues.apache.org/jira/browse/CAMEL-9093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Akitoshi Yoshida resolved CAMEL-9093.
-------------------------------------
    Resolution: Fixed

> Provide an unparsed read mode for olingo2
> -----------------------------------------
>
>                 Key: CAMEL-9093
>                 URL: https://issues.apache.org/jira/browse/CAMEL-9093
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-olingo2
>            Reporter: Akitoshi Yoshida
>            Assignee: Akitoshi Yoshida
>             Fix For: 2.16.0
>
>
> Currently, the result from the read operation is fully parsed and instantiated as one of the olingo2's object. This is suitable when when you intend to directly access some part of the data using oligno2's API. But if you want to access it later or run some generic processing over it, It will be nice to have an unparsed read mode. Having this mode at the olingo2 component, one can combine the API specific operations and the generic operations.
> I am thinking of adding "uread" as the unparsed version of "read".



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)