[
https://issues.apache.org/jira/browse/OLINGO-193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14209308#comment-14209308
]
Michael Bolz commented on OLINGO-193:
-------------------------------------
Hi [~lior.okman],
thanks for your contribution.
I created a [feature
branch|https://git-wip-us.apache.org/repos/asf?p=olingo-odata2.git;a=shortlog;h=refs/heads/OLINGO-193_SpringSupport]
for better discussion.
* First discussion point is the location of the new module. Like other
extensions (e.g. JPA) it could be better to have the module on level above the
lib.
* Second is about the licence. But as I have seen Spring (Beans) is released
under _Apache Licence 2.0_ so we here only have to add it in according
_Distribution_ files.
* Third is (for next contribution) please run a build to prevent checkstyle
violations (e.g. line length > 120 chars) ;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: spring.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)
