[ 
https://issues.apache.org/jira/browse/OLINGO-103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13859878#comment-13859878
 ] 

ASF subversion and git services commented on OLINGO-103:
--------------------------------------------------------

Commit f8638bb7a910fd44f4bd88d0368df760aa189db5 in branch refs/heads/master 
from [~chandan.v.a]
[ 
https://git-wip-us.apache.org/repos/asf?p=incubator-olingo-odata2.git;h=f8638bb 
]

[OLINGO-103] Expose ODataJPAResponseBuilder for External Usage

Signed-off-by: Chandan V A <[email protected]>


> Expose ODataJPAResponseBuilder for External Usage
> -------------------------------------------------
>
>                 Key: OLINGO-103
>                 URL: https://issues.apache.org/jira/browse/OLINGO-103
>             Project: Olingo
>          Issue Type: Improvement
>          Components: odata2-jpa
>            Reporter: Chandan V.A
>            Assignee: Chandan V.A
>             Fix For: V2 1.1.0
>
>
> At times it is required to write an own OData - JPA Processor instead of 
> using the default OData - JPA processor - 
> org.apache.olingo.odata2.jpa.processor.core.ODataJPAProcessorDefault. 
> One could implement a OData JPA processor by extending the 
> org.apache.olingo.odata2.jpa.processor.api.ODataJPAProcessor class. The class 
> encapsulates an instance for processing OData request 
> (org.apache.olingo.odata2.jpa.processor.api.access.JPAProcessor). 
> However to build an OData response from a JPA Entity for a given OData 
> request there is no such instance encapsulated.
> Hence extend ODataJPAProcessor class to encapsulate a OData JPA Response 
> builder which can be used by the subclasses for building OData Responses from 
> JPA Entity.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Reply via email to