[
https://issues.apache.org/jira/browse/OLINGO-193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14267667#comment-14267667
]
Michael Bolz commented on OLINGO-193:
-------------------------------------
Hi [~lior.okman],
I take a look into your contribution and for me it looks good.
Hence I merged it and additional I have done a minor code clean up and renamed
the artifact to {{olingo-odata2-spring}} to be compliant with the other modules
(see [last
commit|https://git-wip-us.apache.org/repos/asf?p=olingo-odata2.git;a=commit;h=92531140bb369a98a12c6a85f3f8aac08fb803bc]).
Additional I have updated the
[example|https://github.com/mibo/olingo-spring-cxf/commit/0ac150938d8f6d5466739ef85995cdacd7ffb653].
>From my point of view this actual version addresses the spring integration
>issue and is in addition well enough separated from the main/core Olingo/OData
>library parts.
So if it is ok for you we could probably merge this into the master. What do
you think?
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
> Affects Versions: V2 2.0.1
> Environment: Spring
> Reporter: Jan Penninkhof
> Assignee: Michael Bolz
> Priority: Minor
> Labels: spring
> 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/[email protected]/msg02186.html
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
