You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@olingo.apache.org by bu...@apache.org on 2013/12/10 10:40:54 UTC
svn commit: r889833 - in /websites/staging/olingo/trunk/content: ./
doc/tutorials/osgi.html
Author: buildbot
Date: Tue Dec 10 09:40:53 2013
New Revision: 889833
Log:
Staging update by buildbot for olingo
Modified:
websites/staging/olingo/trunk/content/ (props changed)
websites/staging/olingo/trunk/content/doc/tutorials/osgi.html
Propchange: websites/staging/olingo/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue Dec 10 09:40:53 2013
@@ -1 +1 @@
-1549797
+1549798
Modified: websites/staging/olingo/trunk/content/doc/tutorials/osgi.html
==============================================================================
--- websites/staging/olingo/trunk/content/doc/tutorials/osgi.html (original)
+++ websites/staging/olingo/trunk/content/doc/tutorials/osgi.html Tue Dec 10 09:40:53 2013
@@ -77,7 +77,7 @@
<p>There is a difficulty in relation to class loading because of Apache Olingo core bundle has to load a specific custom service implementation without having a direct dependency to it.</p>
<p>In Apache Olingo OData2 Version 1.0.0 we solve this issue as follow: </p>
<h3 id="servlet-filter-in-osgi">Servlet Filter in OSGi</h3>
-<p>It is assumed that an OData service implementation is deployed as a native web application (war) or as web application bundle (rfc66). In both cases the Apache Olingo core bundle is not aware of this application and its classloader cannot load applications service factory by default. </p>
+<p>It is assumed that an OData service implementation is deployed as a native web application (war) or as web application bundle (OSGi Enterprise Expert Group on the RFC66 Web Container specification). In both cases the Apache Olingo core bundle is not aware of this application and its classloader cannot load applications service factory by default. </p>
<p>Adding this servlet filter to the service servlet configuration can solve this problem. The filter can bind the application classloader to the servlet request object, which is then used by the Apache Olingo core bundle to load applications factory class. </p>
<div class="codehilite"><pre><span class="kd">public</span> <span class="kd">class</span> <span class="nc">ServiceFactoryFilter</span> <span class="kd">implements</span> <span class="n">Filter</span> <span class="o">{</span>