[
https://issues.apache.org/jira/browse/OLINGO-32?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13807853#comment-13807853
]
Chandan V.A commented on OLINGO-32:
-----------------------------------
Hi Georgi,
JPA stack already uses the Edm annotations that are specific for defining
Function imports. But I am thinking loud if we use these EDM annotations as
part of JPA models (as you have suggested) then my only concern is we are
mixing the JPA models with EDM. To me these two are different meta models and
mostly we could keep them separate.
WDYT?
regards
Chandan
> 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
> Reporter: Michael Bolz
> Priority: Minor
>
> 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)
