[
https://issues.apache.org/jira/browse/OLINGO-1018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15469931#comment-15469931
]
Santosh kumar commented on OLINGO-1018:
---------------------------------------
Hi [~mirbo],
This is nice to have and will remove duplicaiton in the custom code. In the
feature branch I see that the class {{CustomODataJPAProcessor.java}} extends
the newly created class {{ODataJPADefaultProcessor.java}} which again extends
the existing class {{ODataJPAProcessorDefault.java}} without introducing any
new logic to the existing code. Any specific reason for this (having a new
ODataJPADefaultProcessor instead of direclty extending
ODataJPAProcessorDefault) ?
Also when I override {{readEntity}}, I would also want to update the request
parameters like (filter expression, $top, $expand) . Do you think it is
feasible to provide methods that will allow updation of these parameters as
well. similar requirement applies for other methods also
(ex:createEntity,updateEntity etc...) ?
Thanks and Regards,
Santosh
> 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)
