You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@olingo.apache.org by "Alexander Parr (JIRA)" <ji...@apache.org> on 2018/02/06 09:47:00 UTC
[jira] [Created] (OLINGO-1233) Make method buildQuery of
org.apache.olingo.odata2.jpa.processor.core.access.data.JPAQueryBuilder
public
Alexander Parr created OLINGO-1233:
--------------------------------------
Summary: Make method buildQuery of org.apache.olingo.odata2.jpa.processor.core.access.data.JPAQueryBuilder public
Key: OLINGO-1233
URL: https://issues.apache.org/jira/browse/OLINGO-1233
Project: Olingo
Issue Type: New Feature
Components: odata2-jpa
Affects Versions: V2 2.0.10
Environment: SAP Cloud Platform
Reporter: Alexander Parr
Hi community,
we are using Olingo JPA Processor to generate an OData Service. By registering an EntityListener in our JPA class, we hook in the logic of some calls, to have some app specific behaviour which can't be provided by Olingo.
However, we like to make use of, whats implemented by Olingo JPA already - the generation of a JPQL database statement out of a OData request and adjust the statement to our needs. Right now this is hardly possible, because the method doing that is marked as private. The method I would use to do that would be buildQuery of class JPAQueryBuilder 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#L181]
Therefore, I would like to raise a feature request to make method buildQuery public to support a implementation in an EntityListener which bases on whats supported by Olingo already.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)