[
https://issues.apache.org/jira/browse/OLINGO-32?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13837704#comment-13837704
]
Michael Bolz commented on OLINGO-32:
------------------------------------
With [this
commit|https://git-wip-us.apache.org/repos/asf?p=incubator-olingo-odata2.git;a=commit;h=09344a5bc0f2c370a44aec218c1d9ea0bfae10a9]
the dependency from _api-annotation_ to _api_ is removed.
Therefore the {{EdmSimpleTypeKind}} and {{EdmMultiplicity}} are replaced by
{{EdmType}} and {{Multiplicity}}.
[~chandan.v.a]: Can you please take a look into the result and comment if the
changes are suitable for the JPA processor as well.
If it look good for you we can start the merge with the master branch (master
-> feature), rename the _annotation sub-modules_ and then bring the feature
branch into the master.
If all works well we get it done till end of this week and before the next
release ;o)
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)
