[jira] [Resolved] (OLINGO-193) Olingo on Spring implementation scenarion

["Michael Bolz (JIRA)" <ji...@apache.org>]

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

Michael Bolz resolved OLINGO-193.
---------------------------------
       Resolution: Fixed
    Fix Version/s: V2 2.0.2

Merged Feature branch with [commit: \[OLINGO-193\] Merge branch 'OLINGO-193_SpringSupport'|https://git-wip-us.apache.org/repos/asf?p=olingo-odata2.git;a=commit;h=b2b42b1e4387c2b3c6e89521062c7ed4d6bf4feb] into actual master branch. 

> Olingo on Spring implementation scenarion
> -----------------------------------------
>
>                 Key: OLINGO-193
>                 URL: https://issues.apache.org/jira/browse/OLINGO-193
>             Project: Olingo
>          Issue Type: New Feature
>          Components: odata2-core
>    Affects Versions: V2 2.0.1
>         Environment: Spring
>            Reporter: Jan Penninkhof
>            Assignee: Michael Bolz
>            Priority: Minor
>              Labels: spring
>             Fix For: V2 2.0.2
>
>         Attachments: move-up.diff, reuse.diff, root-locator-reuse.diff, spring-core-olingo.diff, spring.diff, unittests.diff
>
>
> Currently only a imlementation scenario using CXFNonSpringJaxrsServlet is provided. However, to implement OLingo while bootstrapping Spring at the same time, this scenario won't work. Instead probably CXFServlet should be used instead.
> However, CXFServlet has quite a different API and Olingo currently doesn't have wiring to that API.
> It would be excellent if there would be a version of Olingo that could work in a Spring environment as well, e.g. to allow for reuse of existing Spring components.
> Please also refer to a discussion on this topic in the mail-archive:
> https://www.mail-archive.com/dev@olingo.incubator.apache.org/msg02186.html



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