[
https://issues.apache.org/jira/browse/OLINGO-1018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15468178#comment-15468178
]
Michael Bolz commented on OLINGO-1018:
--------------------------------------
For feedback/comments/testing of this improvement/feature I created the
[feature branch
OLINGO-1018-JPA_API_DefaultProcessor|https://git1-us-west.apache.org/repos/asf?p=olingo-odata2.git;a=shortlog;h=refs/heads/OLINGO-1018-JPA_API_DefaultProcessor].
The idea is to provide an abstract {{ODataJPAProcessorDefault}} within the API
which can be {{extended}} with the option to only override/implement the
required methods (e.g. {{readEntitySet}}).
As example following [custom processor was created in the reference
scenario|https://github.com/mibo/olingo-odata2/blob/JPA_PublicDefaultProcessor/odata2-jpa-processor/jpa-ref/src/main/java/org/apache/olingo/odata2/jpa/processor/ref/util/CustomODataJPAProcessor.java#L42].
The API change is backward compatible and will not break any existing
implementation.
Feedback welcome ;o)
Best Regards, Michael
> Add an ODataJPAProcessorDefault into JPA API
> --------------------------------------------
>
> Key: OLINGO-1018
> URL: https://issues.apache.org/jira/browse/OLINGO-1018
> Project: Olingo
> Issue Type: New Feature
> Components: odata2-jpa
> Affects Versions: V2 2.0.7
> Reporter: Michael Bolz
> Assignee: Michael Bolz
> Priority: Minor
> Fix For: V2 2.0.8
>
>
> Add an {{ODataJPAProcessorDefault}} into JPA API for easier extension of
> default JPA processor handling of different OData methods (e.g.
> {{readEntity}}).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
