Thanks for the reply. Yeah I agree trying out if it works can be best possible test.
Regards, Vikram Pancholi On Wed, Jul 16, 2014 at 12:52 PM, Bolz, Michael <[email protected]> wrote: > Hi Vikram, > > I'am currently work on serialization and also try to simplify existing > transfer objects. > But IMHO it is better to have such small transfer objects rather then > several adapters which have to be implemented. > Perhaps an approach with a combination of Java Annotations and Domain > Objects/POJOs could also be nice. > > If you want you could create an enhancement issue in JIRA and start with a > "Proof Of Concept" branch for the adapter idea. > That way we could discuss this topic and perhaps find a solution which > than can be contributed by you. > > Kind regards, > Michael > > > > > On 16.07.14 07:21, "Vikram Pancholi" <[email protected]> wrote: > > >Hi, > > While going through the code base for Olingo 4.0. I found the following > >flow > >1. OData request parsing eg "/employee" -- i.e. entityset request for all > >employee > >2. Request execution to provide Resultant data -- say array of employee > >pojo (clarify if wrong) > >3. The resultant data would be mapped to "OData" entity beans including > >property and links. > >4. The Serialization mechanism then serializes the entities to json / json > >with metadata/atom etc format as requested. > > > > > >My query here is pertaining to data sets which span complex entity > >structures/links/nested entities , would it be better to skip to create > >transfer objects i.e. "OData" entities and write down some sort of > >adapters > >to serialize straight from domain entities to relevant OData content. > > > >Regards, > >Vikram Pancholi >
