[
https://issues.apache.org/jira/browse/OLINGO-32?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13835957#comment-13835957
]
Chandan V.A commented on OLINGO-32:
-----------------------------------
Hi Michael,
Regarding
1) I took the parameter modes IN, OUT and INOUT from CSDL specification
assuming they can be used for transforming stored procedure definitions into
EDMFunctionImports. Initially these annotations were defined not specific to
JPA instead can be used outside the scope of JPA. But I dont have any specific
example or use case from JPA side to have these modes as of now. Hence we could
defer the addition of these modes until such a use case arises.
2) JPA processor currently ignores those Java methods that are annotated with
ReturnType.NONE.
3) JPA processor currently ignores those facets with default values that are
not greater than 0. So we can stick to -1.
4) I agree.
Meanwhile I will adapt the JPA processor Library to use the EdmFunction*
annotations in 1.1.0 and also do support the older annotations.
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
> 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)
