Google Git
Sign in
apache / netbeans-docs / refs/heads/asf-site / . / content / 9.0 / javadoc / org-netbeans-modules-editor-settings-storage / overview-summary.html
blob: cd25bdfbf593f78cfe268ae565a7f3ee534c0d9a [file] [log] [blame]
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<!-- NewPage -->
<html lang="en">
<head>
<!-- Generated by javadoc (1.8.0_181) on Fri Sep 14 11:36:16 BST 2018 -->
<title>Overview (Editor Settings Storage)</title>
<meta name="date" content="2018-09-14">
<link rel="stylesheet" type="text/css" href="javadoc.css" title="Style">
<script type="text/javascript" src="script.js"></script>
</head>
<body>
<script type="text/javascript"><!--
try {
if (location.href.indexOf('is-external=true') == -1) {
parent.document.title="Overview (Editor Settings Storage)";
}
}
catch(err) {
}
//-->
</script>
<noscript>
<div>JavaScript is disabled on your browser.</div>
</noscript>
<!-- ========= START OF TOP NAVBAR ======= -->
<div class="topNav"><a name="navbar.top">
<!-- -->
</a>
<div class="skipNav"><a href="#skip.navbar.top" title="Skip navigation links">Skip navigation links</a></div>
<a name="navbar.top.firstrow">
<!-- -->
</a>
<ul class="navList" title="Navigation">
<li class="navBarCell1Rev">Overview</li>
<li>Package</li>
<li>Class</li>
<li>Use</li>
<li><a href="overview-tree.html">Tree</a></li>
<li><a href="deprecated-list.html">Deprecated</a></li>
<li><a href="index-files/index-1.html">Index</a></li>
<li><a href="help-doc.html">Help</a></li>
</ul>
<div class="aboutLanguage">org.netbeans.modules.editor.settings.storage/1 1.53.1 </div>
</div>
<div class="subNav">
<ul class="navList">
<li>Prev</li>
<li>Next</li>
</ul>
<ul class="navList">
<li><a href="index.html?overview-summary.html" target="_top">Frames</a></li>
<li><a href="overview-summary.html" target="_top">No&nbsp;Frames</a></li>
</ul>
<ul class="navList" id="allclasses_navbar_top">
<li><a href="allclasses-noframe.html">All&nbsp;Classes</a></li>
</ul>
<div>
<script type="text/javascript"><!--
allClassesLink = document.getElementById("allclasses_navbar_top");
if(window==top) {
allClassesLink.style.display = "block";
}
else {
allClassesLink.style.display = "none";
}
//-->
</script>
</div>
<a name="skip.navbar.top">
<!-- -->
</a></div>
<!-- ========= END OF TOP NAVBAR ========= -->
<div class="header">
<h1 class="title">Editor Settings Storage<br/><span style='font-style:normal; font-size:medium; font-weight:normal; background-color:#e0a0a0;'><a href='http://wiki.netbeans.org/API_Stability#Friend' target='_blank'>Friend, Private or Third Party</a></span></h1>
</div>
<div class="header">
<p>See: <a href="#overview.description">Description</a></p>
</div>
<div class="contentContainer">
<table class="overviewSummary" border="0" cellpadding="3" cellspacing="0" summary="Editor Settings Storage table, listing packages, and an explanation">
<caption><span>Editor Settings Storage</span><span class="tabEnd">&nbsp;</span></caption>
<tr>
<th class="colFirst" scope="col">Package</th>
<th class="colLast" scope="col">Description</th>
</tr>
<tbody>
<tr class="altColor">
<td class="colFirst"><a href="org/netbeans/modules/editor/settings/storage/api/package-summary.html">org.netbeans.modules.editor.settings.storage.api</a></td>
<td class="colLast">&nbsp;</td>
</tr>
<tr class="rowColor">
<td class="colFirst"><a href="org/netbeans/modules/editor/settings/storage/spi/support/package-summary.html">org.netbeans.modules.editor.settings.storage.spi.support</a></td>
<td class="colLast">&nbsp;</td>
</tr>
</tbody>
</table>
</div>
<div class="contentContainer"><a name="overview.description">
<!-- -->
</a>
<div class="block"><p>
<p>
The <code>editor/settings/storage</code> module provides friend
EditorSettingsStorageAPI
comprising classes in the <code>org.netbeans.modules.editor.settings.storage.api</code>
package. It also defines the structure of the settings storage and the structure
of XML files with settings. The following XML files are supported.
</p>
<ul>
<li>Fonts &amp; Colors - contains colorings that define various attributes
for rendering text tokens in the editor.<br>
<a href="http://www.netbeans.org/dtds/EditorFontsColors-1_1.dtd">EditorFontsColors-1_1.dtd</a><code>-//NetBeans//DTD Editor Fonts and Colors settings 1.1//EN</code>
</li>
<li>Key Bindings - contains definitions of keyboard shortcust and their
associated editor actions.<br>
<a href="http://www.netbeans.org/dtds/EditorKeyBindings-1_1.dtd">EditorKeyBindings-1_1.dtd</a><code>-//NetBeans//DTD Editor KeyBindings settings 1.1//EN</code>
</li>
</ul>
<h3>Profiles and setting folders</h3>
<p>
The setting files are stored in <code>MimeLookup</code> in the folders hierarchy
under the <code>Editors/</code> folder on the default filesystem. The storage follows
the main principle of <code>MimeLookup</code> and allows to define mime type
specific settings as well as settings that apply for all editors. This is achieved
by placing the setting files in the appropriate folder (i.e. in the mime type
folder such as <code>Editors/&lt;mime-type&gt;</code> or in the <code>Editors/</code>
folder itself for the global settings).
</p>
<p>
No matter whether the files are stored in <code>Editors/</code> or in a mime type
specific folder their further position relative to that folder and their meaning
is the same.
</p>
<p>
Both font &amp; colors and key bindings are grouped in so called profiles that
allow user switching quickly between predefined sets of colorings or key bindings. An
example of profiles can be key bindings for NetBeans, Eclipse and Emacs. Each of those
profiles defines keyboard shortcuts for IDE actions that are known from other products.
Another example is the profiles defining normal and inverse color schemes.
In Netbeans they are called NetBeans and CityLights.
</p>
<p>
The <code>editor/settings/storage</code> module dedicates a special folder for
each profile and stores all the profile related files in that folder.
</p>
<h4>Special profiles and mime types</h4>
<p>
The module provides a special treatment for profiles with names starting with
the <code>"test"</code> string. These profiles are handled as a temporary in-memory
profiles, which are not persisted to the disk. They are mainly used for 'preview'
purposes in the Options dialog.
</p>
<p>
The module also recognizes special mime paths, which <code>String</code> representation
starts with the <code>"test*_"</code> string (e.g. <code>"test123ed_text/x-java"</code>)
and provides MimeLookup for those mime paths. The contents of MimeLookup for those
special mime paths is basically the same as MimeLookup for the mime path without the
leading <code>test*_</code> string, but it contains <code>FontColorsSettings</code>
and <code>KeyBindingSettings</code> instances specially constructed for the 'test'
mime type. Again this is mainly used for 'preview' purposes by the Options dialog.
</p>
<p>
Since this functionality is defacto an API it is being tracked as
SpecialProfilesAndMimeTypesAPI.
</p>
<h3>User changes and defaults</h3>
<p>
The editor settings storage is organized in the way that allows storing user
changes separately from the default values provided by modules. This is useful
when a users wants to reset their profiles back to the original values shipped
with the product. This is achieved by defining a special subfolder called
<code>Defaults</code> for every profile. The default colorings and key bindings
provided by modules are then registered in this <code>Defaults</code> subfolder
while user changes are stored directly in the profile's folder. When restoring the
original values the files with user changes are simply deleted and the profile
is reloaded from the default files.
</p>
<h4>Font &amp; color files</h4>
<p>
<b>Since version 1.10</b> the storage module does not require coloring files to be
called any special name. The coloring profiles and files are expected to be
registered by modules under a special folder called <code>FontsColors</code>. The
structure below shows an example of registering several different coloring files
for all editors and the text/x-java mime type.
</p>
<pre xml:space="preserve">
Editors
|- FontsColors
| |- NetBeans
| |- Defaults
| |- foo.xml
| |- bar.xml
|- text
|- x-java
|- FontsColors
|- NetBeans
|- Defaults
|- xyz.xml
|- abc.xml
</pre>
<p>
In order to distinguish files containing token-related colorings from those
with highlight-related colorings the storage module recognizes a special file
attribute called <code>nbeditor-settings-ColoringType</code>, which value can
either be <code>token</code> or <code>highlight</code>. If a coloring file does
not specify this attribute it is automatically expected to contain token-related
colorings.
</p>
<p>
Generally, the files with default values are stored in <code>Defaults</code>
subfolders while the files with user changes are stored directly in the
profile's folder.
</p>
<p>
The default profile for font &amp; colors is called 'NetBeans'.
</p>
<p>
<b>Prior to version 1.10</b> the storage module expected colorings in the
three different types of files. They are still recognized to support
backwards compatibility, but modules are suggusted to use the new registration
scheme. All of those three files had the same structure, but different purpose.
</p>
<ul>
<li>
<code>coloring.xml</code> - defines colorings used for rendering tokens from
a particular language (i.e. mime type).
</li>
<li>
<code>defaultColoring.xml</code> - defines language neutral colorings, which
can be used as fallback for language specific colorings. This file can only
be specified in the <code>Editors/&lt;profile-name&gt;/Defaults</code> folders.
If specified in a mime type subfolder it will be ignored.
</li>
<li>
<code>editorColoring.xml</code> - defines colorings that do not apply for
tokens. These colorings define for example the color for highlighting the row
with a caret, etc. They are not mime type specific and can only be specified
in the <code>Editors/&lt;profile-name&gt;/Defaults</code> folders.
If specified in a mime type subfolder it will be ignored.
</li>
</ul>
<h4>Key bindings files</h4>
<p>
<b>Since version 1.10</b> modules can provide their keybindings in multiple files
placed under the special folder called <code>Keybindings</code> and its profiles'
subfolders. Similarily as for colorings the files with default key bindings are stored in <code>Defaults</code>
subfolder and user changes are stored in files directly in the profile's folder.
The example below shows registration of several keybinding files for all editors
and the text/x-java mime type.
</p>
<pre xml:space="preserve">
Editors
|- Keybindings
| |- NetBeans
| |- Defaults
| |- foo.xml
| |- bar.xml
|- text
|- x-java
|- Keybindings
|- NetBeans
|- Defaults
|- xyz.xml
|- abc.xml
</pre>
<p>
<b>Prior to version 1.10</b> the default profile for key bindings, called NetBeans,
had not been stored in its own folder. Therefore the default key bindings for
the NetBeans profile used to be stored directly in
<code>Editors/&lt;mime-type&gt;/Defaults/keybindings.xml</code> and similarily
user changes used to be stored in <code>Editors/&lt;mime-type&gt;/keybindings.xml</code>.
This has been deprecated, but is still supported for backwards compatibility reasons.
</p>
<p>
Also the special mime type called <code>text/base</code>, has been deprecated
and should not be used anymore. It is however still supported to preserve
backwards compatibility.
</p>
<h3>Platform specific settings</h3>
<p>
<b>Since 1.10</b> it is possible to mark setting files as applicable only on a certain
platform (a.k.a. operating system). This was mainly introduced for keybindings,
which are generally platform sensitive settings, but can be used for any other
setting type supported by the storage module.
</p>
<p class="nonnormative">
Some platforms (eg. Mac) define their own special rules for the use of some
combinations of keystrokes (eg. ctrl+Q closes the app) that applications on that
platform have to obey. NetBeans mitigates this problem by introducing a special
module ide/applemenu, which is only loaded on Mac and which overrides
<code>keybindings.xml</code> files provided by some Netbeans modules (eg. editor and java).
This approach works albeit some severe limitations. However with introducing
multiple setting files this would no longer be practical, which is why platform
specific settings have been introduced.
</p>
<p>
The storage module recognizes a special file attribute for marking
platform specific setting files called <code>nbeditor-settings-targetOS</code>.
The rules for its use follow.
</p>
<ul>
<li>
Any file that does not define <code>nbeditor-settings-targetOS</code> is loaded
on all platforms. All such files will be loaded exactly in the same order as
they appear on the system filesystem.
</li>
<li>
If a file defines <code>nbeditor-settings-targetOS</code> attribute, but its
value does not correspond to the current Operating System, the file is ignored.
</li>
<li>
If a file defines <code>nbeditor-settings-targetOS</code> attribute and its
value designates the current Operating System, the file will be loaded.
Furthermore, any such a file will be loaded <b>after</b> other files in the
same folder that do not define this attribute and therefore its settings will
<b>override</b> settings from those other files.
</li>
<li>
If there is more files that define <code>nbeditor-settings-targetOS</code>
attribute and are eligible for loading on the current Operating System,
they will be loaded in the same order as they appear on the system filesystem.
</li>
</ul>
<p>
The available values that can be used for the <code>nbeditor-settings-targetOS</code>
attribute are the string names of the <code>OS_*</code> constants in <code>org.openide.util.Utilities</code>
class. So, for example the following file will only be loaded on MacOS and its settings
will override settings from all other files that do not specify the target OS attribute.
</p>
<pre xml:space="preserve">
&lt;folder name="Editors"&gt;
&lt;folder name="Keybindings"&gt;
&lt;folder name="NetBeans"&gt;
&lt;folder name="Defaults"&gt;
&lt;file name="keybindings-for-mac.xml" url="..."&gt;
&lt;attr name="nbeditor-settings-targetOS" stringvalue="OS_MAC"/&gt;
&lt;/file&gt;
&lt;/folder&gt;
&lt;/folder&gt;
&lt;/folder&gt;
&lt;/folder&gt;
</pre>
</p>
<h3>What is New (see <a href="apichanges.html">all changes</a>)?</h3>
<ul>
<!--Search for dates that are later or equal to 1997-09-01 in
.-->
<!--Checking date 2015-3-6 with count of newer 0--><!--year ok-->
<li>Mar 6 '15 <a href="apichanges.html#version-1.49">Module split</a>
<p>
Basic infrastructure for settings separated to a library.
</p>
</li>
<!--Checking date 2013-9-17 with count of newer 1--><!--year ok-->
<li>Sep 17 '13 <a href="apichanges.html#issue-231735">Implement profiles for annotations coloring</a>
<p>
<p>
<code>EditorSettings</code> is extended to handle saving and loading annotations colorings for any profile.
</p>
<pre xml:space="preserve">
Class org.netbeans.modules.editor.settings.storage.api.EditorSettings
[sigtest] "E5.2 - Adding abstract methods" : method public abstract void org.netbeans.modules.editor.settings.storage.api.EditorSettings.setAnnotations(java.lang.String,java.util.Map)
[sigtest] "E5.2 - Adding abstract methods" : method public abstract java.util.Map org.netbeans.modules.editor.settings.storage.api.EditorSettings.getAnnotations(java.lang.String)
[sigtest] "E5.2 - Adding abstract methods" : method public abstract java.util.Map org.netbeans.modules.editor.settings.storage.api.EditorSettings.getAnnotationDefaults(java.lang.String)
[sigtest]
</pre>
</p>
</li>
<!--Checking date 2013-2-21 with count of newer 2--><!--year ok-->
<li>Feb 21 '13 <a href="apichanges.html#issue-226111">Detect preferences override and support inheritance</a>
<p>
<p>
<code>OverridePreferences</code> can be used to detect whether the setting is defined for
the specific MIME type, or inherited from default ('all languages') settings.
</p>
<p>
During options editing, <code>MemoryPreferences</code> can be used to create Preferences
object, that propagates changes to its (persistent) delegate upon flush().
</p>
</p>
</li>
<!--Checking date 2009-7-16 with count of newer 3--><!--year ok-->
<li>Jul 16 '09 <a href="apichanges.html#version-1.21">EditorSettings.PROP_MIME_TYPES</a>
<p>
<p>
Adding <code>EditorSettings.PROP_MIME_TYPES</code> to notify about changes in mimetypes returned
from <code>EditorSettings.getAllMimeTypes()</code> and <code>EditorSettings.getMimeTypes()</code>.
</p>
</p>
</li>
<!--Checking date 2008-2-14 with count of newer 4--><!--year ok-->
<li>Feb 14 '08 <a href="apichanges.html#version-1.17">SPI refinements</a>
<p>
<p>
The <code>createReader</code> and <code>createWriter</code> methods
of <code>StorageDescription</code> now have second parameter, which
is a mime path string of the file being read or writter respectively.
</p>
<p>
The <code>StorageReader.getMimePath</code> method was added alongside
with a new constructor that takse two parameters <code>FileObject</code>
that the reader is dealing with and the mime path <code>String</code> of
that file.
</p>
</p>
</li>
<!--Checking date 2007-12-6 with count of newer 5--><!--Skipped as the amount of changes is too big-->
<!--Checking date 2007-11-28 with count of newer 6--><!--Skipped as the amount of changes is too big-->
<!--Checking date 2007-3-21 with count of newer 7--><!--Skipped as the amount of changes is too big-->
<!--Checking date 2007-2-5 with count of newer 8--><!--Skipped as the amount of changes is too big-->
<!--Checking date 2006-12-30 with count of newer 9--><!--Skipped as the amount of changes is too big-->
<!--Checking date 2006-11-13 with count of newer 10--><!--Skipped as the amount of changes is too big-->
</ul>
<h3>Use Cases</h3>
<answer id="arch-usecases">
<h5>New Options Dialog</h5>
<p>
The friend API provided by this module is used only by the new options dialog. It
is not expected to have any other clients or users. The API gives the options
dialog a read/write access to the editor settings storage allowing it to implement
UI for maintaining the settings.
</p>
<h5>Defining a coloring</h5>
<p>
Various modules need to provide predefined font a colors for text tokens from
languages they support. An example of such a module is <code>java/editor</code>
which defines colorings for tokens in java files. Defining colorings is as simple
as writing an XML file with the appropriate information. The example below shows
how to do that.
</p>
<pre xml:space="preserve">
&lt;?xml version="1.0" encoding="UTF-8"?&gt;
&lt;!DOCTYPE fontscolors PUBLIC "-//NetBeans//DTD Editor Fonts and Colors settings 1.1//EN" "http://www.netbeans.org/dtds/EditorFontsColors-1_1.dtd"&gt;
&lt;fontscolors&gt;
&lt;fontcolor name="mylang-keyword" foreColor="0000CC" default="keyword"&gt;
&lt;font style="bold" /&gt;
&lt;/fontcolor&gt;
&lt;/fontscolors&gt;
</pre>
<p>
Please see the
<a href="http://www.netbeans.org/dtds/EditorFontsColors-1_1.dtd" shape="rect">http://www.netbeans.org/dtds/EditorFontsColors-1_1.dtd</a>
for more details.
</p>
<h5>Defining a key binding</h5>
<p>
As well as providing predefined colorings modules need to provide predefined
key bindings. This can be accomplished by writing another simple XML file.
</p>
<pre xml:space="preserve">
&lt;?xml version="1.0" encoding="UTF-8"?&gt;
&lt;!DOCTYPE bindings PUBLIC "-//NetBeans//DTD Editor KeyBindings settings 1.1//EN" "http://www.netbeans.org/dtds/EditorKeyBindings-1_1.dtd"&gt;
&lt;bindings&gt;
&lt;bind actionName="goto-source" key="O-O"/&gt;
&lt;/bindings&gt;
</pre>
<p>
Please see the
<a href="http://www.netbeans.org/dtds/EditorKeyBindings-1_1.dtd" shape="rect">http://www.netbeans.org/dtds/EditorKeyBindings-1_1.dtd</a>
for more details.
</p>
</answer>
<h3>Exported Interfaces</h3>
This table lists all of the module exported APIs
with
defined stability classifications. It is generated
based on answers to questions about the architecture
of the module. <a href="architecture-summary.html">Read them all</a>...
<a name="group-java">
<h5>Group of java interfaces</h5>
</a>
<table cellpadding="1" cellspacing="0" border="0" class="tablebg" width="100%">
<tr>
<td>
<table border="0" cellpadding="3" cellspacing="1" width="100%">
<tr class="tablersh">
<td align="CENTER" width="25%"><span class="titlectable">Interface Name</span></td><td align="CENTER" width="10%"><span class="titlectable">In/Out</span></td><td align="CENTER" width="10%"><span class="titlectable">Stability</span></td><td align="CENTER"><span class="titlectable">Specified in What Document?</span></td>
</tr>
<tr class="tabler">
<td>EditorSettingsStorageAPI</td><td>Exported</td><td><a href="http://wiki.netbeans.org/API_Stability#Friend">Friend</a></td><td><a name="java-EditorSettingsStorageAPI"></a></td>
</tr>
<tr class="tabler">
<td>SpecialProfilesAndMimeTypesAPI</td><td>Exported</td><td><a href="http://wiki.netbeans.org/API_Stability#Friend">Friend</a></td><td><a name="java-SpecialProfilesAndMimeTypesAPI"></a></td>
</tr>
</table>
</td>
</tr>
</table>
<p></p>
<a name="group-dtd">
<h5>Group of dtd interfaces</h5>
</a>
<table cellpadding="1" cellspacing="0" border="0" class="tablebg" width="100%">
<tr>
<td>
<table border="0" cellpadding="3" cellspacing="1" width="100%">
<tr class="tablersh">
<td align="CENTER" width="25%"><span class="titlectable">Interface Name</span></td><td align="CENTER" width="10%"><span class="titlectable">In/Out</span></td><td align="CENTER" width="10%"><span class="titlectable">Stability</span></td><td align="CENTER"><span class="titlectable">Specified in What Document?</span></td>
</tr>
<tr class="tabler">
<td>EditorFontsColors-1_1.dtd</td><td>Exported</td><td><a href="http://wiki.netbeans.org/API_Stability#Official">Official</a></td><td><a name="dtd-EditorFontsColors-1_1.dtd"><a href="http://www.netbeans.org/dtds/EditorFontsColors-1_1.dtd">
.../dtds/EditorFontsColors-1_1.dtd</a>
<p></p>
<p></p>
<code>-//NetBeans//DTD Editor Fonts and Colors settings 1.1//EN</code>
<p></p>
</a></td>
</tr>
<tr class="tabler">
<td>EditorKeyBindings-1_1.dtd</td><td>Exported</td><td><a href="http://wiki.netbeans.org/API_Stability#Official">Official</a></td><td><a name="dtd-EditorKeyBindings-1_1.dtd"><a href="http://www.netbeans.org/dtds/EditorKeyBindings-1_1.dtd">
.../dtds/EditorKeyBindings-1_1.dtd</a>
<p></p>
<p></p>
<code>-//NetBeans//DTD Editor KeyBindings settings 1.1//EN</code>
<p></p>
</a></td>
</tr>
</table>
</td>
</tr>
</table>
<p></p>
<h3>Implementation Details</h3>
<h5>Where are the sources for the module?</h5>
<p>
<p>
The sources for the module are in the
<a href="http://hg.netbeans.org/" shape="rect">NetBeans Mercurial repositories</a>.
</p>
</p>
<h5>What do other modules need to do to declare a dependency on this one, in addition to or instead of a plain module dependency?</h5>
Nothing.
<p>
Read more about the implementation in the <a href="architecture-summary.html">answers to
architecture questions</a>.
</p></div>
</div>
<!-- ======= START OF BOTTOM NAVBAR ====== -->
<div class="bottomNav"><a name="navbar.bottom">
<!-- -->
</a>
<div class="skipNav"><a href="#skip.navbar.bottom" title="Skip navigation links">Skip navigation links</a></div>
<a name="navbar.bottom.firstrow">
<!-- -->
</a>
<ul class="navList" title="Navigation">
<li class="navBarCell1Rev">Overview</li>
<li>Package</li>
<li>Class</li>
<li>Use</li>
<li><a href="overview-tree.html">Tree</a></li>
<li><a href="deprecated-list.html">Deprecated</a></li>
<li><a href="index-files/index-1.html">Index</a></li>
<li><a href="help-doc.html">Help</a></li>
</ul>
<div class="aboutLanguage">org.netbeans.modules.editor.settings.storage/1 1.53.1 </div>
</div>
<div class="subNav">
<ul class="navList">
<li>Prev</li>
<li>Next</li>
</ul>
<ul class="navList">
<li><a href="index.html?overview-summary.html" target="_top">Frames</a></li>
<li><a href="overview-summary.html" target="_top">No&nbsp;Frames</a></li>
</ul>
<ul class="navList" id="allclasses_navbar_bottom">
<li><a href="allclasses-noframe.html">All&nbsp;Classes</a></li>
</ul>
<div>
<script type="text/javascript"><!--
allClassesLink = document.getElementById("allclasses_navbar_bottom");
if(window==top) {
allClassesLink.style.display = "block";
}
else {
allClassesLink.style.display = "none";
}
//-->
</script>
</div>
<a name="skip.navbar.bottom">
<!-- -->
</a></div>
<!-- ======== END OF BOTTOM NAVBAR ======= -->
<p class="legalCopy"><small><span class="footnote">Built on September 14 2018.&nbsp;&nbsp;|&nbsp;&nbsp; Copyright &#169; 2017-2018 Apache Software Foundation. All Rights Reserved.</span></small></p>
</body>
</html>