You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@camel.apache.org by "Dhiraj Bokde (JIRA)" <ji...@apache.org> on 2014/09/11 22:27:33 UTC

[jira] [Updated] (CAMEL-7806) Olingo2 component doesn't support namespaces and entity container names for batch requests

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

Dhiraj Bokde updated CAMEL-7806:
--------------------------------
    Description: 
Olingo2 component had an underlying assumption that all entity sets for an OData service would be in its default entity container. But designating containers as default is optional in OData. 
So the component needs to account for fully qualified resource paths like entity-container.entity-set

  was:
Olingo2 component had an underlying assumption that all entity sets for an OData service would be in its default entity container. But designating containers as default is optional in OData. 
So the component needs to account for fully qualified resource paths like namespace.entity-container.entity-set


> Olingo2 component doesn't support namespaces and entity container names for batch requests
> ------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-7806
>                 URL: https://issues.apache.org/jira/browse/CAMEL-7806
>             Project: Camel
>          Issue Type: Bug
>    Affects Versions: 2.14.0
>            Reporter: Dhiraj Bokde
>            Assignee: Dhiraj Bokde
>            Priority: Blocker
>
> Olingo2 component had an underlying assumption that all entity sets for an OData service would be in its default entity container. But designating containers as default is optional in OData. 
> So the component needs to account for fully qualified resource paths like entity-container.entity-set



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