[
https://issues.apache.org/jira/browse/OLINGO-32?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13823369#comment-13823369
]
Michael Bolz commented on OLINGO-32:
------------------------------------
Hi together,
the past few days I committed the changes in the {{Edm*}} annotation within the
{{olingo-odata2-api-annotation-incubating}} module (see branch
'PocEdmAnnotationsExtension: ).
Currently their exists redundant annotations which are used by the annotation
extension or the JPA extension.
This are:
* {{Facets}} / {{EdmFacets}}
* {{FunctionImports}} / {{EdmFunctionImport}}
* {{Parameter}} / {{EdmFunctionImportParameter}}
Currently not used by the edm annotation extension is {{Documentation}}. It is
possible to remove this annotation?
IMHO we for consistence we should only use the {{Edm*}} annotations.
@Chandan: You are familiar with the JPA extension, hence could you please take
a look into the JPA parts whether it is possible to replace above mentioned
annotations with their {{Edm*}} counterpart?
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)
