[
https://issues.apache.org/jira/browse/OLINGO-193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14225925#comment-14225925
]
Michael Bolz commented on OLINGO-193:
-------------------------------------
Hi [~lior.okman],
I pushed your attached diffs into the [feature
branch|https://git-wip-us.apache.org/repos/asf?p=olingo-odata2.git;a=commit;h=a339d2956d7dd892acd2f67893c1a608e796ad0e].
But actual I didn't checked all parts of your contribution.
I hope I can do this till next week so that we can start a discussion on the
dev mailing list about merge of this feature branch into the master.
Furthermore I had some little problem with your second patch because I couldn't
sign it. As result I applied the changes in my local repo and then pushed it
with me as author. I hope this is OK for you.
For next contributions you could create the patch in the _mbox format_ please.
Therefore you can use {{git format-patch -M origin/OLINGO-193_SpringSupport}}.
More documentation can be found here: [Git Patch
Contribution|http://git-scm.com/book/be/v2/Distributed-Git-Contributing-to-a-Project#_project_over_email].
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)
