[
https://issues.apache.org/jira/browse/OLINGO-1034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15849886#comment-15849886
]
Michael Bolz commented on OLINGO-1034:
--------------------------------------
Hi [~Santosh Kumar],
Sorry for the late response but I had to find some spare time to take a look
into your contribution.
Now I wanted to start taking a look into but it seems that the attached
diff/patch file is not correct.
Perhaps the diff was between the wrong commits or something else is wrong.
Hence I want to ask if you please can do a rebase of your contribution to the
latest master version and afterward create a new patch [as described in our
official contribution
documentation|http://olingo.apache.org/contribute.html#develop-the-according-bugfix-feature].
Best Regards, Michael
> Provide Call backs for CRUD operations
> --------------------------------------
>
> Key: OLINGO-1034
> URL: https://issues.apache.org/jira/browse/OLINGO-1034
> Project: Olingo
> Issue Type: New Feature
> Components: odata2-core, odata2-jpa
> Affects Versions: V2 2.0.7
> Reporter: Santosh kumar
> Labels: features
> Attachments: olingo-odata2.diff
>
>
> OData V2.0.7 doesn't have exit points for CRUD operations on Entities.
> Instead of exit points Olingo supports extending its API class
> {{ODataJPAProcessorDefault}} for any custom CRUD operation. The drawback of
> this approach is that the developer has to duplicate all the operations even
> if only {{readEntity}} has to be customized. Also any modification to the
> request parameters of these operations will require re-writing the Olingo
> code again.
> The proposal is to introduce a call back mechanism(similar to existing debug
> call back) which allows the developer to introduce custom code for CRUD
> operations (ex: {{readEntity}}). This approach also prevents Olingo code
> duplication in client code
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
