[
https://issues.apache.org/jira/browse/OLINGO-1048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15698171#comment-15698171
]
Michael Bolz commented on OLINGO-1048:
--------------------------------------
Hi [~aparr],
I guess the changes fit your use case.
At least it enables exception message propagation via the
{{createApplicationError}} method so IMHO it is worth to bring it on master.
If you think it should be adapter please reopen the issue and give feedback.
Best Regards, Michael
> Exception Handling in Class ODataJPAQueryExtensionEntityListener
> ----------------------------------------------------------------
>
> Key: OLINGO-1048
> URL: https://issues.apache.org/jira/browse/OLINGO-1048
> Project: Olingo
> Issue Type: New Feature
> Affects Versions: V2 2.0.6
> Environment: SAP HANA Cloud Platform
> Reporter: Alexander Parr
> Assignee: Michael Bolz
> Priority: Critical
> Labels: ODataJPAQueryExtensionEntityListener, entitylistener,
> getQuery, jpa
> Attachments: 0001-OLINGO-1048-Add-exception-for-EntityListeners.patch
>
>
> Hi all,
> I'm extending class ODataJPAQueryExtensionEntityListener in order to modify
> the sql query to our needs in getQuery methods. In some cases I like to
> return no entry / query (e.g. the user has not the sufficient role) which is
> not possible currently as the default query will be build in case one returns
> null see
> https://github.com/apache/olingo-odata2/blob/master/odata2-jpa-processor/jpa-core/src/main/java/org/apache/olingo/odata2/jpa/processor/core/access/data/JPAQueryBuilder.java#L74
> on the other hand there are cases in which I like to throw and error message
> of type ODataException in method getQuery to propagate this information to
> the consumer instead of returning an empty list.
> Best
> Alex
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
