[ 
https://issues.apache.org/jira/browse/OLINGO-562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Thierry Templier updated OLINGO-562:
------------------------------------
    Description: 
Hello,

I have implemented a Spring support for Olingo v4 server side. It allows to 
define declaratively within your Spring configuration:

* EDM provider (see file 
src/test/resources/applicationContext-edm-provider-namespace.xml)
* HTTP handler 
(src/test/resources/applicationContext-http-handler-namespace.xml)

        <olingo:http-handler id="httpHandler" edm-provider="edmProvider">
                <olingo:reference 
uri="../v4.0/cs02/vocabularies/Org.OData.Core.V1.xml">
                        <olingo:include key="Org.OData.Core.V1" value="Core"/>
                </olingo:reference>
                <olingo:processor ref="testProcessor"/>
        </olingo:http-handler>


A dedicated servlet is provided to get an instance of ODataHttpHandler from a 
Spring container and use it to handle request.

You can find enclosed the corresponding code.

I don't how such code can be integrated to Olingo. I think that it corresponds 
more to an extension than something to put in the Olingo core.

Feel free to give me your feedback.
Thierry

  was:
Hello,

I have implemented a Spring support for Olingo v4 server side. It allows to 
define declaratively within your Spring configuration:

* EDM provider (see file 
src/test/resources/applicationContext-edm-provider-namespace.xml)
* HTTP handler 
(src/test/resources/applicationContext-http-handler-namespace.xml)

A dedicated servlet is provided to get an instance of ODataHttpHandler from a 
Spring container and use it to handle request.

You can find enclosed the corresponding code.

I don't how such code can be integrated to Olingo. I think that it corresponds 
more to an extension than something to put in the Olingo core.

Feel free to give me your feedback.
Thierry


> Spring support for Olingo v4 server
> -----------------------------------
>
>                 Key: OLINGO-562
>                 URL: https://issues.apache.org/jira/browse/OLINGO-562
>             Project: Olingo
>          Issue Type: Bug
>    Affects Versions: (Java) V4 4.0.0-beta-02
>         Environment: Java, Spring 4
>            Reporter: Thierry Templier
>         Attachments: olingo-server-v4-spring.zip
>
>
> Hello,
> I have implemented a Spring support for Olingo v4 server side. It allows to 
> define declaratively within your Spring configuration:
> * EDM provider (see file 
> src/test/resources/applicationContext-edm-provider-namespace.xml)
> * HTTP handler 
> (src/test/resources/applicationContext-http-handler-namespace.xml)
>       <olingo:http-handler id="httpHandler" edm-provider="edmProvider">
>               <olingo:reference 
> uri="../v4.0/cs02/vocabularies/Org.OData.Core.V1.xml">
>                       <olingo:include key="Org.OData.Core.V1" value="Core"/>
>               </olingo:reference>
>               <olingo:processor ref="testProcessor"/>
>       </olingo:http-handler>
> A dedicated servlet is provided to get an instance of ODataHttpHandler from a 
> Spring container and use it to handle request.
> You can find enclosed the corresponding code.
> I don't how such code can be integrated to Olingo. I think that it 
> corresponds more to an extension than something to put in the Olingo core.
> Feel free to give me your feedback.
> Thierry



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to