[
https://issues.apache.org/jira/browse/OLINGO-193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14211215#comment-14211215
]
Michael Bolz commented on OLINGO-193:
-------------------------------------
Hi [~lior.okman],
thanks for second patch/contribution. I will check and give feedback.
Regarding the license I will check whether an update within distribution module
(_LICENSE_, _NOTICE_, etc.) is necessary.
Normally during {{mvn package}} the checkstyle plugin validates some rules (and
fail the build if those are not meet).
If you are using Eclipse best practice is to import
{{src/eclipse/eclipse-*.xml}} files and run a _code cleanup_ on the new/changed
code.
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, 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)
