[
https://issues.apache.org/jira/browse/OLINGO-126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephan Klevenz resolved OLINGO-126.
------------------------------------
Resolution: Done
Please have a look into ODataSingleProcessor:readServiceDocument(). You can
override this method and pass any service root while creating a response:
final ODataResponse response = EntityProvider.writeServiceDocument(contentType,
entityDataModel, serviceRoot);
The same should be possible for JPAProcessor.
Metadata is usually free of urls, right? No action here.
> Use of an OData service behind an Apache reverse proxy
> ------------------------------------------------------
>
> Key: OLINGO-126
> URL: https://issues.apache.org/jira/browse/OLINGO-126
> Project: Olingo
> Issue Type: Question
> Affects Versions: V2 1.0.0
> Reporter: M Carissimi
> Assignee: Stephan Klevenz
> Fix For: V2 1.2.0
>
>
> Hello,
> we have an OData service built on Olingo which we package in a web archive
> running a CXFNonSpringJaxrsServlet. The module is deployed to a Glassfish
> 3.1.2.2 domain which sits behind an Apache HTTP server with reverse proxy
> capabilities. The Apache 2.2 virtual host configuration has the following
> entries:
> ProxyPass /olingo http://appsdev1:10156/ODataPrototypeOlingo
> ProxyPassReverse /olingo http://appsdev1:10156/ODataPrototypeOlingo
> Using this configuration we can successfully access the OData service using
> URL:
> http://server/olingo/service.svc/entityset
> The feeds that we get back from the service contain links with URLs for the
> actual server running Glassfish:
> http://appsdev1:10156/ODataPrototypeOlingo/service.svc/entityset
> Is there a way to dynamically change the links generated in Olingo to use the
> root URL used in the request so that links have URLs similar to:
> http://server/olingo/service.svc/entityset
> Regards
> Miki
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
