[
https://issues.apache.org/jira/browse/OLINGO-104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14008823#comment-14008823
]
Stephan Klevenz commented on OLINGO-104:
----------------------------------------
Function Import do allow only simple types as parameter. See section 3.3 at [1].
[1] http://www.odata.org/documentation/odata-version-2-0/uri-conventions/
> JPA Documentation Update: Adding Non JPA Entities as Function Import Return
> Types
> ---------------------------------------------------------------------------------
>
> Key: OLINGO-104
> URL: https://issues.apache.org/jira/browse/OLINGO-104
> Project: Olingo
> Issue Type: Improvement
> Components: odata2-documentation
> Reporter: Chandan V.A
> Assignee: Deepashree
> Attachments: SalesOrderHeaderProcessor.java
>
>
> Hello Deepa,
> Two new features have been introduced in OData2-JPA processor where
> A) One can extend the EDM generated from JPA Models by implementing the
> Interface method
> org.apache.olingo.odata2.jpa.processor.api.model.JPAEdmExtension.extendJPAEdmSchema.
> B) One can add non JPA Entity Types to the EDM and use the same as Function
> Imports return type.
> Refer to [1] for more details.
> The documentation [2] needs to be updated with details on how one can add a
> non JPA Entity as complex types to EDM and then use the same as the return
> type in a function import.
> [1] https://issues.apache.org/jira/browse/OLINGO-28
> [2] http://olingo.incubator.apache.org/doc/tutorials/jpafunctionimport.html
> Regards
> Chandan
--
This message was sent by Atlassian JIRA
(v6.2#6252)
