[
https://issues.apache.org/jira/browse/OLINGO-32?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13839905#comment-13839905
]
Michael Bolz commented on OLINGO-32:
------------------------------------
Hi Chandan,
the module {{odata-annotation-processor-core}} contains the {{ListsProcessor}}
so that the {{-processor}} suffix fit.
Currently the {{ListsProcessor}} exposes two interfaces ({{ListsDataSource}}
and {{ValueAccess}}) which then enforce an own {{-processor-api}} module
(based on our current project structure).
In addition we _could/should_ create an own interface for the
{{ListsProcessor}} too.
In conclusion I think we should create following submodules:
* {{annotation-processor-api}}: API/Interfaces
* {{annotation-processor-core}}: Implementation
* {{annotation-processor-webref}}: Reference Scenario/Integration Tests
Kind regards,
Michael
> Introduce (Java) Annotations for definition of EDM
> --------------------------------------------------
>
> Key: OLINGO-32
> URL: https://issues.apache.org/jira/browse/OLINGO-32
> Project: Olingo
> Issue Type: New Feature
> Affects Versions: V2 1.1.0
> Reporter: Michael Bolz
> Assignee: Michael Bolz
> Priority: Minor
> Fix For: V2 1.1.0
>
>
> The idea is to create your model as POJOs which then can be annotated with
> special {{@EdmXXX}} (Java) annotations to define the EDM for an OData Service.
> Based on these annotation then the {{edmx}} document ({{$metadata}}) can be
> generated as well as a generic {{Processor}} ({{ODataSingleProcessor}}) for
> e.g. {{JSON}} can be written.
> As initial contribution and starting point for discussions about this feature
> a branch with name {{PocEdmAnnotationsExtension}} is created with a basic
> Proof of Concept.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
