Hans,

I'm moderating this by replying only to the Dev and User lists of Olingo.

Regards,
Dave

Sent from my iPhone

> On Sep 7, 2017, at 2:57 AM, Hans Kruse <kr...@hanskruse.eu> wrote:
> 
> Why where [OLINGO-1166]  and [OLINGO-1152] not included. Patches with tests 
> were submitted?
> Are they going to be be included and if so when?
> 
> Regards,
> Hans Kruse
> 
> 
> Op di 5 sep. 2017 om 16:55 schreef Christian Amend <chri...@apache.org>:
>> Hello,
>> 
>> we announce that Apache Olingo 4.4.0 has been released.
>> 
>> This is the second stable Olingo release version for OData Version 4
>> (see specification [1] and new features [2]).
>> 
>> This release is available for download:
>> http://olingo.apache.org/doc/odata4/download.html
>> New Tutorials and documentation are also available:
>> http://olingo.apache.org/doc/odata4/index.html
>> Available also in central maven repository:
>> http://search.maven.org/#search%7Cga%7C1%7Cg%3A%22org.apache.olingo%22%20AND%20v%3A%224.4.0%22
>> 
>> If you would like to get involved please write to: <u...@olingo.apache.org>
>> Or subscribe to our mailing list: http://olingo.apache.org/support.html
>> 
>> Apache Olingo is a Java library which enables developers to
>> implement OData service providers (server) and consumers (clients).
>> 
>> The Open Data Protocol (OData, http://www.odata.org/) is an open protocol
>> to allow the creation and consumption of queryable and interoperable
>> RESTful APIs in a simple and standard way.
>> 
>> 
>> [1]: 
>> http://docs.oasis-open.org/odata/odata/v4.0/odata-v4.0-part1-protocol.html
>> [2]: 
>> http://docs.oasis-open.org/odata/new-in-odata/v4.0/cn01/new-in-odata-v4.0-cn01.html
>> 
>> Release Notes - Olingo - Version 4.4.0
>> ---------------------------------------------------
>> Link: 
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314520&version=12338257
>> 
>> Bug
>> [OLINGO-753] - URIUtils.buildFunctionInvokeURI() build a wrong uri
>> when the uri parameter contains /$count
>> [OLINGO-917] - $entity request with $select system option always fails to 
>> parse
>> [OLINGO-975] - Olingo client sends incorrect types for collection members
>> [OLINGO-1008] - Metadata Parser is unable to parse external references
>> of Microsoft dynamics CRM Odata metadata
>> [OLINGO-1033] - V4: @odata.type annotation incorrect for primitive types
>> [OLINGO-1046] - Whitespaces in functions not allowed
>> [OLINGO-1058] - OData V4.0: NextLink Support in streaming to enable
>> server side pagination
>> [OLINGO-1064] - ComplexType is deserialized as Primitive Type if the
>> value is NULL
>> [OLINGO-1073] - Collections with derived complex types - wrong odata.type
>> [OLINGO-1076] - Validating Query Options for correct syntax
>> [OLINGO-1080] - Support Entity Iterator in batch
>> [OLINGO-1083] - OData V4 Singleton has EntityType instead of Type
>> attribute in XML metadata
>> [OLINGO-1102] - ODataErrorResponseChecker.checkResponse(...) not
>> return detail error message for ODataServerErrorException
>> [OLINGO-1104] - NavigationLink missing from JSON with expand and 
>> metadata=full
>> [OLINGO-1107] - UriDecoder should use java.net.URLDecoder
>> [OLINGO-1111] - EntityResponse's location building not taking
>> property's facets in to consideration
>> [OLINGO-1112] - Compound Key not handled correctly EntityResponse
>> [OLINGO-1132] - Type information is lost when primitive properties
>> with null value is updated
>> Improvement
>> [OLINGO-846] - Flexible URL parsing for System Query Options
>> [OLINGO-1028] - V4: $filter statements on navigation properties
>> [OLINGO-1099] - Refactor the V4 $levels implementation
>> New Feature
>> [OLINGO-1059] - OData V4.0: Cross Service EDM
>> [OLINGO-1077] - OData V4.0: EntityIterator count support
>> Task
>> [OLINGO-1171] - V4: Build 4.4.0 release
>> Test
>> [OLINGO-1106] - Custom Query options in batch request
>> 
>> Best Regards,
>> Christian
> 
> -- 
> Hans Kruse
> 
> ☎: +31683968991
> 
> ✉  kr...@hanskruse.eu
> 
> Disclaimer
> 
> E-mail correspondence  is secret only if encrypted. 
> Digital signatures are only recognized as a signature when using public key 
> cryptography.
> E-mail messages without digital signature are not legally binding and 
> included disclaimers are not relevant.

Reply via email to