You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@olingo.apache.org by "Santosh kumar (JIRA)" <ji...@apache.org> on 2016/10/14 09:35:21 UTC
[jira] [Created] (OLINGO-1034) Provide Call backs for CRUD
operations
Santosh kumar created OLINGO-1034:
-------------------------------------
Summary: 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
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.4#6332)