[
https://issues.apache.org/jira/browse/OLINGO-562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14311388#comment-14311388
]
Michael Bolz commented on OLINGO-562:
-------------------------------------
Hi [~templth],
yes, there are some guidelines:
* code formatting rules (for eclipse) can be found in folder {{src/eclipse}}
and checkstyle rules in {{src/checkstyle}}.
* all files require the _Apache License Header_. To check if your project
fulfil this you can run a {{maven}} build with profile {{-P build.quality}}
(e.g. {{mvn package -Pbuild.quality}}) which runs the Apache RAT check.
* Root package should be {{org.apache.olingo.ext}} and for _Spring extension_ I
suggest then {{org.apache.olingo.ext.spring}}.
Kind regards,
Michael
> Spring support for Olingo v4 server
> -----------------------------------
>
> Key: OLINGO-562
> URL: https://issues.apache.org/jira/browse/OLINGO-562
> Project: Olingo
> Issue Type: New Feature
> Affects Versions: (Java) V4 4.0.0-beta-02
> Environment: Java, Spring 4
> Reporter: Thierry Templier
> Attachments: olingo-server-v4-spring.zip
>
>
> Hello,
> I have implemented a Spring support for Olingo v4 server side. It allows to
> define declaratively within your Spring configuration:
> * EDM provider (see file
> src/test/resources/applicationContext-edm-provider-namespace.xml)
> * HTTP handler
> (src/test/resources/applicationContext-http-handler-namespace.xml)
> A dedicated servlet is provided to get an instance of ODataHttpHandler from a
> Spring container and use it to handle request.
> You can find enclosed the corresponding code.
> I don't how such code can be integrated to Olingo. I think that it
> corresponds more to an extension than something to put in the Olingo core.
> Feel free to give me your feedback.
> Thierry
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
