[
https://issues.apache.org/jira/browse/OLINGO-1018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15474679#comment-15474679
]
Michael Bolz commented on OLINGO-1018:
--------------------------------------
Hi [~Santosh Kumar],
Thanks for the feedback.
I had two reasons in mind.
First to have the {{ODataJPADefaultProcessor}} as an _abstract_ class so that
someone who wants customization explicitly has to extend it.
Second to be sure about backward compatibility ;o)
But after your feedback and re-check into the current solution I saw that I
forgot the _abstract_ and that the {{ODataJPAProcessorDefault}} is only used
within the _core_ module.
I have changed the last solution a little and updated the [feature
branch|https://git1-us-west.apache.org/repos/asf?p=olingo-odata2.git;a=commit;h=03457349196c8788f7865e4478071c14d77c9ea3].
It would be really nice if you could take a look into and give feedback ;o)
And what you have mentioned in the second section sound interesting, however it
sounds like another (new) issue ;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)
