Hi Ramesh, I am still looking into the merge. There was some parts of the code which I wanted to discuss on the mailinglist before merging it into the master. So I don`t know if it will make it into the first release.
My main concern with the code was that the first part of the context URL String is used to resolve the EntitySet which is needed for some OData Annotations. On one hand this is nice because we do not have to change the API between minimal and full. On the other hand it is not clear to a user where and how we extract the EntitySet information. WDYT? How did you solve this within the XMLSerializer where you needed the EntitySet information? Best Regards, Christian -----Original Message----- From: Ramesh Reddy [mailto:[email protected]] Sent: Dienstag, 25. August 2015 17:08 To: [email protected] Subject: Re: [INFO] End of the Google Summer of Code 2015 Great job Kevin and Christian. Is there a possibility to get the "odata.metadata=full" format support merged into the master now as this is fully defined already in V4 spec? Thanks Ramesh.. ----- Original Message ----- > Hi all, > > The Google Summer of Code 2015 is coming to an end. Since March this year > Kevin Ratnasekera has been working for Apache Olingo as part of the GSoC. As > a result we have odata.metadata=full format support for responses and a > first implementation for the json metadata document format. Once the OData > V4 specification which contains this format definition is released we will > be able to merge this code into the master branch. > > I would like to take this opportunity to thank Kevin a lot for his engagement > during this time and I think he did a great job! > > The Json Metadata Document Implementation can be found here: > https://git-wip-us.apache.org/repos/asf?p=olingo-odata4.git;a=shortlog;h=refs/heads/jsonMetadata > > Best Regards, > Christian >
