[ 
https://issues.apache.org/jira/browse/OLINGO-193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14306635#comment-14306635
 ] 

Stefan Kühnemann commented on OLINGO-193:
-----------------------------------------

Thank you for your e-mail. As of january 23rd 2015 I left SAP and am no longer 
able to answer your e-mail.
Kind regards Stefan Kühnemann

Vielen Dank für Ihre E-mail. Ich habe SAP zum 23.01.2015 verlassen und kann 
daher Ihre E-Mail nicht mehr beantworten.
Mit freundlichen Grüßen Stefan Kühnemann



> 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/[email protected]/msg02186.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to