[
https://issues.apache.org/jira/browse/OLINGO-193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14226254#comment-14226254
]
Michael Bolz commented on OLINGO-193:
-------------------------------------
Hi [~lior.okman],
just to clarify, I want to start a discussion/vote on the developer mailing
list whether your contribution should be merged into the master branch or not.
I'am just a single developer and can not speak for the other developer on
Olingo and hence can not promise that this feature branch is merged into the
master.
But I'am optimistic that we get this feature into Olingo :o)
Yes, please create separate issues for further improvements for Olingo in
combination with Spring.
This make discussions / tracking / merging a lot easier ;o)
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.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)
