Author: nick
Date: Wed Aug 19 15:06:01 2015
New Revision: 1696610
URL: http://svn.apache.org/r1696610
Log:
Republish the site
Modified:
tika/site/publish/1.10/configuring.html
tika/site/publish/1.11/configuring.html
Modified: tika/site/publish/1.10/configuring.html
URL:
http://svn.apache.org/viewvc/tika/site/publish/1.10/configuring.html?rev=1696610&r1=1696609&r2=1696610&view=diff
==============================================================================
--- tika/site/publish/1.10/configuring.html (original)
+++ tika/site/publish/1.10/configuring.html Wed Aug 19 15:06:01 2015
@@ -96,7 +96,12 @@
<li><a href="#Configuring_Mime_Types">Configuring Mime Types</a></li>
<li><a href="#Configuring_Language_Identifiers">Configuring Language
Identifiers</a></li>
<li><a href="#Configuring_Translators">Configuring Translators</a></li>
-<li><a href="#Configuring_the_Service_Loader">Configuring the Service
Loader</a></li></ul></li></ul>
+<li><a href="#Configuring_the_Service_Loader">Configuring the Service
Loader</a>
+<ul>
+<li><a href="#Static">Static</a></li>
+<li><a href="#Dynamic">Dynamic</a></li>
+<li><a href="#Load_Error_Handling">Load Error Handling</a></li></ul></li>
+<li><a href="#Using_a_Tika_Configuration_XML_file">Using a Tika Configuration
XML file</a></li></ul></li></ul>
<div class="section">
<h3><a name="Configuring_Parsers">Configuring Parsers</a></h3>
<p>Through the Tika Config xml, it is possible to have a high degree of
control over which parsers are or aren't used, in what order of preferences
etc. It is also possible to override just certain parts, to (for example) have
"default except for PDF".</p>
@@ -156,22 +161,35 @@
<p>At this time, there is no unified way to configure language identifiers.
While the work on that is ongoing, for now you will need to review the <a
href="./api/">Tika Javadocs</a> to see how individual identifiers are
configured.</p></div>
<div class="section">
<h3><a name="Configuring_Translators">Configuring Translators</a></h3>
-<p>At this time, there is no unified way to configure Translators. While the
work on that is ongoing, for now you will need to review the <a
href="./api/">Tika Javadocs</a> to see how individual Translators are
configured.</p></div>
+<p>At this time, there is no unified way to configure Translators. While the
work on that is ongoing, for now you will need to review the <a
href="./api/">Tika Javadocs</a> to see how individual Translators are
configured.</p><!-- When Translators can have their parameters configured,
mention here about --><!-- specifying which single one to use in the Tika
Config XML --></div>
<div class="section">
<h3><a name="Configuring_the_Service_Loader">Configuring the Service
Loader</a></h3>
<p>Tika has a number of service provider types such as parsers, detectors, and
translators. The <a
href="./api/org/apache/tika/config/ServiceLoader.html">org.apache.tika.config.ServiceLoader</a>
class provides a registry of each type of provider. This allows Tika to create
implementations such as <a
href="./api/org/apache/tika/parser/DefaultParser.html">org.apache.tika.parser.DefaultParser</a>,
<a
href="./api/org/apache/tika/language/translate/DefaultTranslator.html">org.apache.tika.language.translate.DefaultTranslator</a>,
and <a
href="./api/org/apache/tika/detect/DefaultDetector.html">org.apache.tika.detect.DefaultDetector</a>
that can match the appropriate provider to an incoming piece of content.</p>
<p>The ServiceLoader's registry can be populated either statically or
dynamically.</p>
-<p>Static Static loading is the default which requires no configuration. This
configuration options is used in Tika deployments where the Tika JAR files
reside together in the same classloader hierarchy. The services provides are
loaded from provider configuration files located within the tika-parsers JAR
file at META-INF/services.</p>
-<p>Dynamic Dynamic loading may be required if the tika service providers will
reside in different classloaders such as in OSGi. To allow a provider created
in tika-config.xml to utilize dynamically loaded services you need to configure
the ServiceLoader to be dynamic with the following configuration:</p>
+<div class="section">
+<h4>Static<a name="Static"></a></h4>
+<p>Static loading is the default which requires no configuration. This
configuration options is used in Tika deployments where the Tika JAR files
reside together in the same classloader hierarchy. The services provides are
loaded from provider configuration files located within the tika-parsers JAR
file at META-INF/services.</p></div>
+<div class="section">
+<h4>Dynamic<a name="Dynamic"></a></h4>
+<p>Dynamic loading may be required if the tika service providers will reside
in different classloaders such as in OSGi. To allow a provider created in
tika-config.xml to utilize dynamically loaded services you need to configure
the ServiceLoader to be dynamic with the following configuration:</p>
<div>
<pre><properties>
<service-loader dynamic="true"/>
....
-</properties></pre></div>
-<p>The ServiceLoader can contains a handler to deal with errors that occur
during provider initialization. For example if a class fails to initialize
LoadErrorHandler deals with the exception that is thrown. This handler can be
configured to:</p>
-<p>IGNORE - (Default) Do nothing when providers fail to initialize. WARN - Log
a warning when providers fail to initialize. THROW - Throw an exception when
providers fail to initialize.</p></div></div>
+</properties></pre></div></div>
<div class="section">
-<h2>For example to set the LoadErrorHandler to WARN then use the following
configuration: --- <i>properties</i> <i>service-loader
loadErrorHandler="WARN"/</i> .... <i>/properties</i> ---<a
name="For_example_to_set_the_LoadErrorHandler_to_WARN_then_use_the_following_configuration:_---_properties_service-loader_loadErrorHandlerWARN_...._properties_---"></a></h2><!--
When Translators can have their parameters configured, mention here about
--><!-- specifying which single one to use in the Tika Config XML -->
+<h4>Load Error Handling<a name="Load_Error_Handling"></a></h4>
+<p>The ServiceLoader can contains a handler to deal with errors that occur
during provider initialization. For example if a class fails to initialize
LoadErrorHandler deals with the exception that is thrown. This handler can be
configured to:</p>
+<ul>
+<li><tt> IGNORE </tt> - (Default) Do nothing when providers fail to
initialize.</li>
+<li><tt> WARN </tt> - Log a warning when providers fail to initialize.</li>
+<li><tt> THROW </tt> - Throw an exception when providers fail to
initialize.</li></ul>
+<p>For example to set the LoadErrorHandler to WARN then use the following
configuration:</p>
+<div>
+<pre><properties>
+ <service-loader loadErrorHandler="WARN"/>
+ ....
+</properties></pre></div></div></div>
<div class="section">
<h3><a name="Using_a_Tika_Configuration_XML_file">Using a Tika Configuration
XML file</a></h3>
<p>However you call Tika, the System Property of <tt> tika.config </tt> is
checked first, and the Environment Variable of <tt> TIKA_CONFIG </tt> is tried
next. Setting one of those will cause Tika to use your given Tika Config XML
file.</p>
Modified: tika/site/publish/1.11/configuring.html
URL:
http://svn.apache.org/viewvc/tika/site/publish/1.11/configuring.html?rev=1696610&r1=1696609&r2=1696610&view=diff
==============================================================================
--- tika/site/publish/1.11/configuring.html (original)
+++ tika/site/publish/1.11/configuring.html Wed Aug 19 15:06:01 2015
@@ -96,7 +96,12 @@
<li><a href="#Configuring_Mime_Types">Configuring Mime Types</a></li>
<li><a href="#Configuring_Language_Identifiers">Configuring Language
Identifiers</a></li>
<li><a href="#Configuring_Translators">Configuring Translators</a></li>
-<li><a href="#Configuring_the_Service_Loader">Configuring the Service
Loader</a></li></ul></li></ul>
+<li><a href="#Configuring_the_Service_Loader">Configuring the Service
Loader</a>
+<ul>
+<li><a href="#Static">Static</a></li>
+<li><a href="#Dynamic">Dynamic</a></li>
+<li><a href="#Load_Error_Handling">Load Error Handling</a></li></ul></li>
+<li><a href="#Using_a_Tika_Configuration_XML_file">Using a Tika Configuration
XML file</a></li></ul></li></ul>
<div class="section">
<h3><a name="Configuring_Parsers">Configuring Parsers</a></h3>
<p>Through the Tika Config xml, it is possible to have a high degree of
control over which parsers are or aren't used, in what order of preferences
etc. It is also possible to override just certain parts, to (for example) have
"default except for PDF".</p>
@@ -156,22 +161,35 @@
<p>At this time, there is no unified way to configure language identifiers.
While the work on that is ongoing, for now you will need to review the <a
href="./api/">Tika Javadocs</a> to see how individual identifiers are
configured.</p></div>
<div class="section">
<h3><a name="Configuring_Translators">Configuring Translators</a></h3>
-<p>At this time, there is no unified way to configure Translators. While the
work on that is ongoing, for now you will need to review the <a
href="./api/">Tika Javadocs</a> to see how individual Translators are
configured.</p></div>
+<p>At this time, there is no unified way to configure Translators. While the
work on that is ongoing, for now you will need to review the <a
href="./api/">Tika Javadocs</a> to see how individual Translators are
configured.</p><!-- When Translators can have their parameters configured,
mention here about --><!-- specifying which single one to use in the Tika
Config XML --></div>
<div class="section">
<h3><a name="Configuring_the_Service_Loader">Configuring the Service
Loader</a></h3>
<p>Tika has a number of service provider types such as parsers, detectors, and
translators. The <a
href="./api/org/apache/tika/config/ServiceLoader.html">org.apache.tika.config.ServiceLoader</a>
class provides a registry of each type of provider. This allows Tika to create
implementations such as <a
href="./api/org/apache/tika/parser/DefaultParser.html">org.apache.tika.parser.DefaultParser</a>,
<a
href="./api/org/apache/tika/language/translate/DefaultTranslator.html">org.apache.tika.language.translate.DefaultTranslator</a>,
and <a
href="./api/org/apache/tika/detect/DefaultDetector.html">org.apache.tika.detect.DefaultDetector</a>
that can match the appropriate provider to an incoming piece of content.</p>
<p>The ServiceLoader's registry can be populated either statically or
dynamically.</p>
-<p>Static Static loading is the default which requires no configuration. This
configuration options is used in Tika deployments where the Tika JAR files
reside together in the same classloader hierarchy. The services provides are
loaded from provider configuration files located within the tika-parsers JAR
file at META-INF/services.</p>
-<p>Dynamic Dynamic loading may be required if the tika service providers will
reside in different classloaders such as in OSGi. To allow a provider created
in tika-config.xml to utilize dynamically loaded services you need to configure
the ServiceLoader to be dynamic with the following configuration:</p>
+<div class="section">
+<h4>Static<a name="Static"></a></h4>
+<p>Static loading is the default which requires no configuration. This
configuration options is used in Tika deployments where the Tika JAR files
reside together in the same classloader hierarchy. The services provides are
loaded from provider configuration files located within the tika-parsers JAR
file at META-INF/services.</p></div>
+<div class="section">
+<h4>Dynamic<a name="Dynamic"></a></h4>
+<p>Dynamic loading may be required if the tika service providers will reside
in different classloaders such as in OSGi. To allow a provider created in
tika-config.xml to utilize dynamically loaded services you need to configure
the ServiceLoader to be dynamic with the following configuration:</p>
<div>
<pre><properties>
<service-loader dynamic="true"/>
....
-</properties></pre></div>
-<p>The ServiceLoader can contains a handler to deal with errors that occur
during provider initialization. For example if a class fails to initialize
LoadErrorHandler deals with the exception that is thrown. This handler can be
configured to:</p>
-<p>IGNORE - (Default) Do nothing when providers fail to initialize. WARN - Log
a warning when providers fail to initialize. THROW - Throw an exception when
providers fail to initialize.</p></div></div>
+</properties></pre></div></div>
<div class="section">
-<h2>For example to set the LoadErrorHandler to WARN then use the following
configuration: --- <i>properties</i> <i>service-loader
loadErrorHandler="WARN"/</i> .... <i>/properties</i> ---<a
name="For_example_to_set_the_LoadErrorHandler_to_WARN_then_use_the_following_configuration:_---_properties_service-loader_loadErrorHandlerWARN_...._properties_---"></a></h2><!--
When Translators can have their parameters configured, mention here about
--><!-- specifying which single one to use in the Tika Config XML -->
+<h4>Load Error Handling<a name="Load_Error_Handling"></a></h4>
+<p>The ServiceLoader can contains a handler to deal with errors that occur
during provider initialization. For example if a class fails to initialize
LoadErrorHandler deals with the exception that is thrown. This handler can be
configured to:</p>
+<ul>
+<li><tt> IGNORE </tt> - (Default) Do nothing when providers fail to
initialize.</li>
+<li><tt> WARN </tt> - Log a warning when providers fail to initialize.</li>
+<li><tt> THROW </tt> - Throw an exception when providers fail to
initialize.</li></ul>
+<p>For example to set the LoadErrorHandler to WARN then use the following
configuration:</p>
+<div>
+<pre><properties>
+ <service-loader loadErrorHandler="WARN"/>
+ ....
+</properties></pre></div></div></div>
<div class="section">
<h3><a name="Using_a_Tika_Configuration_XML_file">Using a Tika Configuration
XML file</a></h3>
<p>However you call Tika, the System Property of <tt> tika.config </tt> is
checked first, and the Environment Variable of <tt> TIKA_CONFIG </tt> is tried
next. Setting one of those will cause Tika to use your given Tika Config XML
file.</p>
