[
https://issues.apache.org/jira/browse/OLINGO-562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14617105#comment-14617105
]
Jim Basilio commented on OLINGO-562:
------------------------------------
Hi Michael:
I'm just getting going with this but in order to get off the ground I had to
squash the commits on this branch and rebase against master. There was a
conflict in the ext/pom.xml related to karaf/spring .. I'm not familiar enough
with this to know how to effectively deconflict properly. I did have issues
compiling the karaf extension but moving that out of the way (obviously not the
proper solution) cleared it up.
Going to keep working on it to try to integrate to my spring app and test
things out but it seems the branch is a bit broken at the moment w.r.t. master.
Thanks.
jim
> 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: 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.3.4#6332)
