[
https://issues.apache.org/jira/browse/OLINGO-562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14308703#comment-14308703
]
Michael Bolz commented on OLINGO-562:
-------------------------------------
Hi [~templth],
actual all extensions should be separated from the core Olingo framework.
Therefore the extensions have to be placed into a separate folder within the
{{ext}} folder/module without referencing them from the projects parent {{pom}}.
This way we have used for the {{spring extension}} in the {{OData V2}} library
(see also OLINGO-193) and plan to use e.g. for the JPA processor extension (see
OLINGO-552). Based on this the extension is separated from the core (for build
and release) but is included in the according git repository (and hence easy to
find and access for a developer).
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)
