[
https://issues.apache.org/jira/browse/OLINGO-326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Challen resolved OLINGO-326.
----------------------------
Resolution: Fixed
https://git-wip-us.apache.org/repos/asf?p=olingo-odata4.git;a=commit;h=1e8ad44a00ad68a63b2996582096621c887b3f19
> URIbuilder issue on android, and uri format issue of addressing derived types
> -----------------------------------------------------------------------------
>
> Key: OLINGO-326
> URL: https://issues.apache.org/jira/browse/OLINGO-326
> Project: Olingo
> Issue Type: Bug
> Components: odata4-client
> Affects Versions: V4 0.1.0
> Reporter: Challen
> Assignee: Challen
> Fix For: V4 0.1.0
>
>
> 1. URIbuilder issue on android
> UriBuilder.build() issue: it will try to call
> URLEncodedUtils.format(Iterable<>,Charset) method, which works in desktop
> java application, however, throws NoSuchMethodError in android application,
> so need to manually construct the URL by its overload
> URLEncodedUtils.format(List<>,String).
> 2. uri format issue of addressing derived types
> only 'OData Intermediate Conformance Level': MUST support casting to a
> derived type according to [OData-URL] if derived types are present in the
> model.
> so current solution is to add a config for client to query minimal
> conformance level servce. the config is: query URIs in request should contain
> fully qualified type name or not
> Example: http://host/service/Customers/Model.VipCustomer(102) or
> http://host/service/Customers/Model.VipCustomer
--
This message was sent by Atlassian JIRA
(v6.2#6252)
