You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@olingo.apache.org by "Michael Bolz (JIRA)" <ji...@apache.org> on 2015/02/05 05:54:34 UTC
[jira] [Commented] (OLINGO-193) Olingo on Spring implementation
scenarion
[ https://issues.apache.org/jira/browse/OLINGO-193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14306633#comment-14306633 ]
Michael Bolz commented on OLINGO-193:
-------------------------------------
Version {{2.0.2}} of Olingo now includes Spring Support.
See in [Maven Central for this version|http://search.maven.org/#search%7Cga%7C1%7Cg%3A%22org.apache.olingo%22%20AND%20a%3A%22olingo-odata2-spring%22%20AND%20v%3A%222.0.2%22] (or for [Olingo Spring extension|http://search.maven.org/#search%7Cga%7C1%7Cg%3A%22org.apache.olingo%22%20AND%20a%3A%22olingo-odata2-spring%22]).
> 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)