[
https://issues.apache.org/jira/browse/OLINGO-193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14256958#comment-14256958
]
Michael Bolz commented on OLINGO-193:
-------------------------------------
Hi [~lior.okman],
I pushed a new version/state of a possible merge/solution into the [feature
branch|https://git-wip-us.apache.org/repos/asf?p=olingo-odata2.git;a=commit;h=7a596e207e0292419447f11b1df792f1824ca432].
Can you please take a look into and give feedback if this solution fits your
needs.
In addition I have created an [example
project|https://github.com/mibo/olingo-spring-cxf/tree/For-Olingo-7a596e2]
based on Spring and the Olingo ReferenceScenario.
With my current understanding this example is what you want to address with
this issue, or?
Kind regards,
Michael
> 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/[email protected]/msg02186.html
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
