[
https://issues.apache.org/jira/browse/OLINGO-32?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13839975#comment-13839975
]
Michael Bolz commented on OLINGO-32:
------------------------------------
With the [last
commit|https://git-wip-us.apache.org/repos/asf?p=incubator-olingo-odata2.git;a=commit;h=12ea18aed44f33fb58b577887533bf841771bfea]
we have (IMHO) a state to merge into the master branch.
If no one comments here or write on the mailing list any objections against I
will do the merge today.
[~chandan.v.a]: It is no part of this issue, but is it possible that you rename
the folder {{odata2-processor-jpa}} to {{odata2-jpa-processor}} so that it fit
to the project name.
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)
