[
https://issues.apache.org/jira/browse/OLINGO-32?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13836516#comment-13836516
]
Michael Bolz commented on OLINGO-32:
------------------------------------
Hi,
with the last
[commit|https://git-wip-us.apache.org/repos/asf?p=incubator-olingo-odata2.git;a=commit;h=49786b4b7636b9417085bc50301716143766b485]
I added more documentation to the annotation, set the redundant annotation to
{{deprecated}} and fixed/changed some minor issues.
The currently open points and next steps are:
* Decision whether {{EdmSimpleTypeKind}} should be replaced to remove
dependency to _odata-api_ (and doing).
* Renaming of _odata-edm-annotation_ to _odata-annotation-processor_ (or
discussion about another name)
* Merge of _PocEdmAnnotationExtension_ into master branch (includes code
refactoring)
Have I missed something?
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)
