You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@olingo.apache.org by "Lior Okman (JIRA)" <ji...@apache.org> on 2014/12/22 06:54:13 UTC

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

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

Lior Okman updated OLINGO-193:
------------------------------
    Attachment: spring-core-olingo.diff

Separated out the part of the patch that affects the core library.

> 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
>         Environment: Spring
>            Reporter: Jan Penninkhof
>            Assignee: Michael Bolz
>            Priority: Minor
>              Labels: spring
>         Attachments: move-up.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)