[
https://issues.apache.org/jira/browse/OLINGO-562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Bolz closed OLINGO-562.
-------------------------------
Resolution: Won't Fix
Hi,
because the issue is older then two years and affected version was beta is set
I will close this.
For the case that someone has the same issue with current version please reopen.
Regards, Michael
> Spring support for Olingo v4 server
> -----------------------------------
>
> Key: OLINGO-562
> URL: https://issues.apache.org/jira/browse/OLINGO-562
> Project: Olingo
> Issue Type: New Feature
> Affects Versions: (Java) V4 4.0.0-beta-02
> Environment: Java, Spring 4
> Reporter: Thierry Templier
> Assignee: Michael Bolz
> Attachments:
> 0001-OLINGO-562-split-the-code-between-the-generic-part-a.patch,
> olingo-server-v4-spring-20150311.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)
> 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.4.14#64029)
