Author: buildbot
Date: Mon Feb 18 05:56:56 2019
New Revision: 1040560
Log:
Staging update by buildbot for olingo
Modified:
websites/staging/olingo/trunk/content/ (props changed)
websites/staging/olingo/trunk/content/doc/odata2/download.html
websites/staging/olingo/trunk/content/doc/odata2/tutorials/debug.html
websites/staging/olingo/trunk/content/doc/odata4/tutorials/navigation/tutorial_navigation.html
websites/staging/olingo/trunk/content/doc/odata4/tutorials/readep/tutorial_readep.html
Propchange: websites/staging/olingo/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Feb 18 05:56:56 2019
@@ -1 +1 @@
-1853771
+1853782
Modified: websites/staging/olingo/trunk/content/doc/odata2/download.html
==============================================================================
--- websites/staging/olingo/trunk/content/doc/odata2/download.html (original)
+++ websites/staging/olingo/trunk/content/doc/odata2/download.html Mon Feb 18
05:56:56 2019
@@ -106,9 +106,9 @@ implementing <a href="http://odata.org";>
<p>The Apache Olingo OData2 2.0.11 release is a patch release.</p>
<h3 id="commodity-packages">Commodity Packages<a class="headerlink"
href="#commodity-packages" title="Permanent link">¶</a></h3>
<p>The <strong>Olingo Library Core</strong> packages contains the
<em>API</em>, the <em>implementation</em>, the <em>documentation as
JavaDoc</em> and the <em>Reference Scenario</em>.
-The <em>API</em> and the according <em>implementation</em> can be used in a
<em>productive</em> environment.
-The Reference Scenario is a sample and <strong>shall not be used in a
productive</strong> environment.
-The <em>Core Library</em> is developed for the productive usage in business
scenarios.</p>
+The <em>API</em> and the according <em>implementation</em> can be used in a
<em>production</em> environment.
+The Reference Scenario is a sample and <strong>shall not be used in a
production</strong> environment.
+The <em>Core Library</em> is developed for production environment usage in
business scenarios.</p>
<table class="table">
<thead>
<tr>
@@ -144,7 +144,7 @@ The <em>Core Library</em> is developed f
<p>The <strong>Olingo Library Extension</strong> packages contains extensions
which are provided from various contributors in the context of the Olingo open
source project.
The extensions provides convenience for easier consumption or creation of an
OData service like the <em>JPA based processor</em>, the <em>Java Annotation
based processor</em> or the <em>Spring Framework integration</em>.
However the extensions are <em>not optimized regarding performance or
extensibility</em>.
-Interested parties can use the extensions, if they are sufficient for their
scenarios in a productive environment.
+Interested parties can use the extensions, if they are sufficient for their
scenarios in a production environment.
Feature enhancements or optimizations of the extensions have to be done by the
interested parties itself.</p>
<table class="table">
<thead>
Modified: websites/staging/olingo/trunk/content/doc/odata2/tutorials/debug.html
==============================================================================
--- websites/staging/olingo/trunk/content/doc/odata2/tutorials/debug.html
(original)
+++ websites/staging/olingo/trunk/content/doc/odata2/tutorials/debug.html Mon
Feb 18 05:56:56 2019
@@ -107,7 +107,7 @@ h2:hover > .headerlink, h3:hover > .head
<h3 id="debug-support">Debug Support<a class="headerlink"
href="#debug-support" title="Permanent link">¶</a></h3>
<p>The OData V2 error message format is limited to the HTTP status codes and
gives indicators for client errors (status code 4xx) and server errors (5xx).
For development and support this is not sufficient because of more technical
information is needed for doing a deep error analysis.</p>
<p>Apache Olingo has implemented a feature to return more error information
(stack traces, object states, runtime measurements â¦) within a response to
ease the development and support use case.</p>
-<p>For productive uses cases this feature is by default off. The following
explains how to enable the feature and gives options to a service
implementation to switch if on and off e.g. role based or by configuration.</p>
+<p>For uses cases in a production environment this feature is by default off.
The following explains how to enable the feature and gives options to a service
implementation to switch if on and off e.g. role based or by configuration.</p>
<h5 id="debugcallback">DebugCallback<a class="headerlink"
href="#debugcallback" title="Permanent link">¶</a></h5>
<p>The debug feature can be enabled by the following callback
implementation:</p>
<div class="codehilite"><pre><span class="n">public</span> <span
class="n">class</span> <span class="n">MyDebugCallback</span> <span
class="n">implements</span> <span class="n">ODataDebugCallback</span> <span
class="p">{</span>
@@ -247,7 +247,7 @@ the real work.</p>
is requested as described above.</p>
<h3 id="log-and-trace-support">Log and Trace Support<a class="headerlink"
href="#log-and-trace-support" title="Permanent link">¶</a></h3>
<p>Apache Olingo has no dependencies to any specific log and trace api (e.g.
slf4j, log4j â¦) and with that it does not trace anything by default. This is
to keep the library independent from a specific api so that it can be used on
any JEE compliant platform independent from which l&t api is offered
there.</p>
-<p>Anyhow log and trace is required for productive use and the following
recommendations are given:</p>
+<p>Anyhow log and trace is required for most production environments and the
following recommendations are given:</p>
<h5 id="servlet-filter">Servlet Filter<a class="headerlink"
href="#servlet-filter" title="Permanent link">¶</a></h5>
<p>For tracing the http traffic (request url, query parameter, http headers,
response code â¦) to and from the server it is recommended to implement a
servlet filter on top of the service. This is completely independent from the
Apache Olingo OData library and has no restrictions.</p>
<h5 id="service-processor-implementation">Service Processor Implementation<a
class="headerlink" href="#service-processor-implementation" title="Permanent
link">¶</a></h5>
Modified:
websites/staging/olingo/trunk/content/doc/odata4/tutorials/navigation/tutorial_navigation.html
==============================================================================
---
websites/staging/olingo/trunk/content/doc/odata4/tutorials/navigation/tutorial_navigation.html
(original)
+++
websites/staging/olingo/trunk/content/doc/odata4/tutorials/navigation/tutorial_navigation.html
Mon Feb 18 05:56:56 2019
@@ -842,7 +842,7 @@ Check the <em>Links</em> section for mor
</ul>
<hr />
<h1 id="7-appendix-code-snippets">7. Appendix: code snippets<a
class="headerlink" href="#7-appendix-code-snippets" title="Permanent
link">¶</a></h1>
-<p>When reaching the point where your OData service has to become productive
and support complex scenarions, youâll find the following code snippets
useful.</p>
+<p>When reaching the point where your OData service has to become production
ready and support complex scenarions, youâll find the following code snippets
useful.</p>
<h2 id="71-find-the-edmentityset-for-the-navigation-target">7.1. Find the
EdmEntitySet for the navigation target<a class="headerlink"
href="#71-find-the-edmentityset-for-the-navigation-target" title="Permanent
link">¶</a></h2>
<div class="codehilite"><pre><span class="kd">public</span> <span
class="kd">static</span> <span class="n">EdmEntitySet</span> <span
class="nf">getNavigationTargetEntitySet</span><span class="o">(</span><span
class="kd">final</span> <span class="n">UriInfoResource</span> <span
class="n">uriInfo</span><span class="o">)</span> <span class="kd">throws</span>
<span class="n">ODataApplicationException</span> <span class="o">{</span>
Modified:
websites/staging/olingo/trunk/content/doc/odata4/tutorials/readep/tutorial_readep.html
==============================================================================
---
websites/staging/olingo/trunk/content/doc/odata4/tutorials/readep/tutorial_readep.html
(original)
+++
websites/staging/olingo/trunk/content/doc/odata4/tutorials/readep/tutorial_readep.html
Mon Feb 18 05:56:56 2019
@@ -550,7 +550,7 @@ The steps to be followed in the implemen
</pre></div>
-<p>This is only possible, because in our current sample scenario we only
support simple URIs. In a real productive OData service, which supports
navigation and other OData V4 features, the code would be more complex.</p>
+<p>This is only possible, because in our current sample scenario we only
support simple URIs. In a real production environment OData service, which
supports navigation and other OData V4 features, the code would be more
complex.</p>
</li>
<li>
<p><strong>Fetch the data from backend</strong><br />
