blob: 621ec2e6a075aba67cdcc51c9eef20f9ec690088 [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:37:50 BST 2018 -->
<title>Overview (Database Explorer)</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 (Database Explorer)";
}
}
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.db/1 1.68.1 30</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">Database Explorer<br/><span style='font-style:normal; font-size:medium; font-weight:normal; background-color:#ffffff;'><a href='http://wiki.netbeans.org/API_Stability#Official' target='_blank'>Official</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="Database Explorer table, listing packages, and an explanation">
<caption><span>Database Explorer</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/api/db/explorer/package-summary.html">org.netbeans.api.db.explorer</a></td>
<td class="colLast">&nbsp;</td>
</tr>
<tr class="rowColor">
<td class="colFirst"><a href="org/netbeans/api/db/explorer/node/package-summary.html">org.netbeans.api.db.explorer.node</a></td>
<td class="colLast">&nbsp;</td>
</tr>
<tr class="altColor">
<td class="colFirst"><a href="org/netbeans/api/db/explorer/support/package-summary.html">org.netbeans.api.db.explorer.support</a></td>
<td class="colLast">&nbsp;</td>
</tr>
<tr class="rowColor">
<td class="colFirst"><a href="org/netbeans/api/db/sql/support/package-summary.html">org.netbeans.api.db.sql.support</a></td>
<td class="colLast">&nbsp;</td>
</tr>
<tr class="altColor">
<td class="colFirst"><a href="org/netbeans/spi/db/explorer/package-summary.html">org.netbeans.spi.db.explorer</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 Database module provides the
<a href="index.html">DatabaseExplorerAPI</a>
which allows access to the database connections and drivers
defined in the Database Explorer. It allows a client to retrieve the
connection list and their properties, to create new connections and remove
existing ones. The Database Explorer also manages a list of JDBC drivers used to
connect to databases. The API provides access to these drivers and allows
to create new and remove existing drivers.
</p>
<p>
The <a href="index.html">DatabaseExplorerLayerAPI</a>
allows for the declarative registration of database connections and JDBC
drivers in the module layer. Database runtimes (which are representations of
an instance of a database server) can also be registered in the layer.
</p>
<!--
The Actions folder for dbschema and sql files. They should actually be in db/model and db/core, but
those modules don't have Javadoc, therefore the description is here.
-->
<p>
<a href="index.html">Loaders-text-dbschema-Actions</a>
allows extending <code>.dbschema</code> files with own actions by registering them in the
<code>Loaders/text/x-dbschema/Actions</code> folder. Note that this folder is actually provided by the
<code>org-netbeans-modules-dbschema.jar</code> module.
</p>
<p>
<a href="index.html">Loaders-text-sql-Actions</a>
allows extending <code>.sql</code> files with own actions by registering them in the
<code>Loaders/text/x-sql/Actions</code> folder. Note that this folder is actually provided by the
<code>org-netbeans-modules-db-core.jar</code> module.
</p>
<p>
This module also provides a <a href="org/netbeans/api/db/sql/support/package-summary.html">SQLSupportAPI</a>
which provides utilities for working with SQL such as quoting identifiers.
</p>
</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 2013-6-10 with count of newer 0--><!--year ok-->
<li>Jun 10 '13 <a href="apichanges.html#issue-231030">
Configure usage of scrollable cursors.
</a>
<p>
Users can enable or disable using of scrollable cursors, which
can make queries faster, but also can cause problems for some
drivers.
</p>
</li>
<!--Checking date 2013-2-13 with count of newer 1--><!--year ok-->
<li>Feb 13 '13 <a href="apichanges.html#issue-197408">
Enable editting of connection properties for db connections
</a>
<p>
Users can specify connection properties in the UI now.
The properties can be retrieved using new method
DatabaseConnection.getConnectionProperties(). There is also a
new factory method DatabaseConnection.create() that accepts an
object with additional connection properties.
</p>
</li>
<!--Checking date 2010-11-22 with count of newer 2--><!--year ok-->
<li>Nov 22 '10 <a href="apichanges.html#issue-192150">Allow specify display name of the DatabaseConnection</a>
<p>
Allow to specify the display name of the connection as it shows
under the Databases node. Added new factory method to create
database connection with given display name.
</p>
</li>
<!--Checking date 2009-5-6 with count of newer 3--><!--year ok-->
<li>May 6 '09 <a href="apichanges.html#issue-90210">Add a DatabaseConnection.getJDBCDriver() method</a>
<p>
Currently there is no easy way to get the JDBCDriver instance that a
DatabaseConnection will use / used to connect to a database. A
<code>DatabaseConnection.getJDBCDriver()</code> method should be added.
</p>
</li>
<!--Checking date 2008-8-27 with count of newer 4--><!--year ok-->
<li>Aug 27 '08 <a href="apichanges.html#issue-143837">Add ability to ensure a JDBC connection is valid</a>
<p>
This change allows you to ensure that the physical database connection
obtained from a DatabaseConnection is valid or is null .
</p>
</li>
<!--Checking date 2008-8-15 with count of newer 5--><!--Skipped as the amount of changes is too big-->
<!--Checking date 2008-6-27 with count of newer 6--><!--Skipped as the amount of changes is too big-->
<!--Checking date 2008-6-27 with count of newer 6--><!--Skipped as the amount of changes is too big-->
<!--Checking date 2008-6-26 with count of newer 8--><!--Skipped as the amount of changes is too big-->
<!--Checking date 2008-2-26 with count of newer 9--><!--Skipped as the amount of changes is too big-->
<!--Checking date 2007-11-1 with count of newer 10--><!--Skipped as the amount of changes is too big-->
<!--Checking date 2007-10-5 with count of newer 11--><!--Skipped as the amount of changes is too big-->
<!--Checking date 2007-9-12 with count of newer 12--><!--Skipped as the amount of changes is too big-->
<!--Checking date 2007-6-17 with count of newer 13--><!--Skipped as the amount of changes is too big-->
<!--Checking date 2006-7-20 with count of newer 14--><!--Skipped as the amount of changes is too big-->
<!--Checking date 2006-3-17 with count of newer 15--><!--Skipped as the amount of changes is too big-->
<!--Checking date 2005-9-12 with count of newer 16--><!--Skipped as the amount of changes is too big-->
</ul>
<h3>Use Cases</h3>
<answer id="arch-usecases">
<h5>Registering JDBC ../db.drivers</h5>
<p>
An external module can register JDBC drivers. A typical example is a module
which provides integration with a database server. In this case the module
contains the JDBC driver for that database server and uses the Database
Explorer API to add it do the Database Explorer.
</p>
<p>
Another client of this API could be a module providing integration with a J2EE
application server. Sometimes a J2EE application server bundles a database server
for improving the out-of-the-box experience. When the server is registered
in the IDE the JDBC drivers for the bundled database server are added to the Database
Explorer.
</p>
<p>
The drivers are registered by making calls on
<a href="org/netbeans/api/db/explorer/JDBCDriverManager.html" shape="rect">JDBCDriverManager</a> or
by registering an XML file which describes the driver in the module layer.
The XML file is described by the
<a href="http://www.netbeans.org/dtds/jdbc-driver-1_1.dtd" shape="rect">JDBC Driver DTD</a>.
An example of a registration file describing the JDBC driver for PostgreSQL follows:
</p>
<pre xml:space="preserve">
&lt;?xml version='1.0'?&gt;
&lt;!DOCTYPE driver PUBLIC '-//NetBeans//DTD JDBC Driver 1.0//EN' 'http://www.netbeans.org/dtds/jdbc-driver-1_0.dtd'&gt;
&lt;driver&gt;
&lt;name value='postgresql-7'/&gt;
&lt;display-name value='PostgreSQL (v7.0 and later)'/&gt;
&lt;class value='org.postgresql.Driver'/&gt;
&lt;urls&gt;
&lt;url value='file:/folder1/folder2/drivers/pg74.1jdbc3.jar'/&gt;
&lt;/urls&gt;
&lt;/driver&gt;
</pre>
<p>
This file should be registered in the <code>Databases/JDBCDrivers</code> folder of the module layer.
To addres a bundled JAR inside the IDE the nbinst protocol can be used in the URLs:
<code>nbinst:/modules/ext/bundled-driver.jar</code>.
</p>
<h5>Get the underlying JDBC Driver instance for a JDBCDriver</h5>
<p>
You can use the <a href="org/netbeans/api/db/explorer/JDBCDriver.html#getDriver--" shape="rect">JDBCDriver.getDriver()</a>
method to obtain a reference to the underlying JDBC Driver instance. This is useful if you want to use the registered
drivers but create your own JDBC connections independent of the Database Explorer.
</p>
<h5>Retrieving the list of JDBC ../db.drivers</h5>
<p>
When creating a new connection the JDBC driver which it should use can be specified.
A list of all the registered JDBC drivers can be retrieved using
<a href="org/netbeans/api/db/explorer/JDBCDriverManager.html#getDrivers--" shape="rect">JDBCDriverManager.getDrivers()</a>.
</p>
<h5>Registering database runtimes</h5>
<p>
An external module can register new database runtimes. A database runtime
is an abstraction of a database server instance
(usually bundled with the IDE, an integration module or with a J2EE server). It allows a database
server instance to be started and stopped when a connection to this
instance is made in the IDE. Database runtimes are represented by the
<a href="org/netbeans/spi/db/explorer/DatabaseRuntime.html" shape="rect">DatabaseRuntime</a>
SPI interface and are registered in the <code>Databases/Runtimes</code> of the module layer.
</p>
<h5>Creating database connections</h5>
<p>
A module can create new database connections (for example to a bundled database).
New connections can be added by calling
<a href="org/netbeans/api/db/explorer/DatabaseConnection.html#create-org.netbeans.api.db.explorer.JDBCDriver-java.lang.String-java.lang.String-java.lang.String-java.lang.String-boolean-" shape="rect">DatabaseConnection.create()</a>
to create a new DatabaseConnection instance and then
<a href="org/netbeans/api/db/explorer/ConnectionManager.html#addConnection-org.netbeans.api.db.explorer.DatabaseConnection-" shape="rect">ConnectionManager.addConnection()</a> to
add the connection to the Database Explorer.
</p>
<p>
New connections can also be added by registering them in the module layer.
The format of the registration file is described by the
<a href="http://www.netbeans.org/dtds/connection-1_0.dtd" shape="rect">Database Connection DTD</a>.
An example of a registration file describing a connection to a PostgreSQL database follows:
</p>
<pre xml:space="preserve">
&lt;?xml version='1.0'?&gt;
&lt;!DOCTYPE connection PUBLIC '-//NetBeans//DTD Database Connection 1.1//EN' 'http://www.netbeans.org/dtds/connection-1_1.dtd'&gt;
&lt;connection&gt;
&lt;driver-class value='org.postgresql.Driver'/&gt;
&lt;driver-name value='postgres-7'/&gt;
&lt;database-url value='jdbc:postgresql:test'/&gt;
&lt;schema value='public'/&gt;
&lt;user value='test'/&gt;
&lt;password value='cGFzc3dvcmQ='/&gt;
&lt;/connection&gt;
</pre>
<p>
This file should be registered in the <code>Databases/Connections</code> folder
of the module layer.
</p>
<p>
The password element is optional, but if it is included,
its value must be the Base64 encoding of the UTF-8 representation of the
password. Note that the UTF-8 representation of passwords composed entirely of
ASCII characters is the same as their ASCII representation, so for such
passwords all that needs to be done is to convert them to Base64.
</p>
<p>
Base64 encoding serves as a simple scrambling to prevent
accidental revelation of the password. It is not indended to offer any
real security. You can protect the password by assigning appropriate
file protections to the connection XML file.
</p>
<h5>Retrieving and displaying the list of database connections</h5>
<p>
Sometimes the list of connections needs to be displayed somewhere
else in the IDE than the Runtime tab. A typical example is the SQL Editor,
which allows the user to select the database connection which the SQL statement
will be executed against in a combo box in the editor toolbar.
The list of connections can be obtained by calling
<a href="org/netbeans/api/db/explorer/ConnectionManager.html#getConnections--" shape="rect">ConnectionManager.getConnections()</a>,
which returns an array of
<a href="org/netbeans/api/db/explorer/DatabaseConnection.html" shape="rect">DatabaseConnection</a>
instances.
</p>
<p>
The client usually needs to show the display name of the connection. The
display name can be retrieved using the
<a href="org/netbeans/api/db/explorer/DatabaseConnection.html#getDisplayName--" shape="rect">DatabaseConnection.getDisplayName()</a>
method.
</p>
<h5>Retrieving the properties of database connections</h5>
<p>
Sometimes a client needs to retrieve the connection properties, such as the driver class.
An example could be a module for a J2EE server creating a connection pool. The properties can
be retrieved using the <code>getDriverClass()</code>, <code>getDatabaseURL()</code>,
<code>getSchema()</code>, <code>getUser()</code> and <code>getPassword()</code>
methods of the
<a href="org/netbeans/api/db/explorer/DatabaseConnection.html" shape="rect">DatabaseConnection</a>
class.
</p>
<h5>Showing the New Database Connection dialog</h5>
<p>
Usually when displaying a list of connections (usually in a combo box),
the last item is "New Connection", which displays the standard New Database Connection
dialog of the Database Explorer. This can be achieved by calling one of the
<a href="org/netbeans/api/db/explorer/ConnectionManager.html#showAddConnectionDialog-org.netbeans.api.db.explorer.JDBCDriver-" shape="rect">ConnectionManager.showAddConnectionDialog()</a> methods.
</p>
<h5>Remove a database connection</h5>
<p>
A user of this API may want to remove a connection from the list of connections
registered by the Database Explorer. This is done using
<a href="org/netbeans/api/db/explorer/ConnectionManager.html#removeConnection-org.netbeans.api.db.explorer.DatabaseConnection-" shape="rect">ConnectionManager.removeConnection()</a>
</p>
<h5>Connecting to a database</h5>
<p>
A component which provides database functionality (such as the SQL Editor)
will need to connect to a database. This can be achieved using the
<a href="org/netbeans/api/db/explorer/ConnectionManager.html#showConnectionDialog-org.netbeans.api.db.explorer.DatabaseConnection-" shape="rect">DatabaseConnection.showConnectionDialog()</a>
method and the <code>java.sql.Connection</code> instance can be retrieved using the
<a href="org/netbeans/api/db/explorer/DatabaseConnection.html#getJDBCConnection--" shape="rect">getJDBCConnection()</a>
method.
</p>
<p>
If you want to connect to the database without showing a dialog or any kind of UI, you can use the
<a href="org/netbeans/api/db/explorer/ConnectionManager.html#connect-org.netbeans.api.db.explorer.DatabaseConnection-" shape="rect">DatabaseConnection.connect()</a>
method.
</p>
<h5>Test a database connection for validity</h5>
<p>
You may want to test to make sure the underlying physical JDBC connection
obtained from a DatabaseConnection is either valid or null. This is done using the
<a href="org/netbeans/api/db/explorer/DatabaseConnection.html#getJDBCConnection-boolean-" shape="rect">
DatabaseConnection.getJDBCConnection(boolean test)</a>
method, which validates the underlying connection before returning it. If the
connection is invalid, it marks the DatabaseConnection as disconnected and returns null.
</p>
<h5>Displaying the database connections in the UI</h5>
<p>
A component which provides database functionality (such as the SQL Editor
or a module providing support for data sources) will need to let the user
select the a database connection, usually through a combo box.
This can be achieved using the
<a href="org/netbeans/api/db/explorer/support/DatabaseExplorerUIs.html#connect-javax.swing.JComboBox-org.netbeans.api.db.explorer.ConnectionManager-" shape="rect">DatabaseExplorerUIs.connect()</a>
method. The <code>JComboBox</code> passed to the method will be filled with the list of connections as returned by
<a href="org/netbeans/api/db/explorer/ConnectionManager.html#getConnections--" shape="rect">ConnectionManager.getConnections()</a>, followed by a separator
and a <em>New Database Connection</em> item which will display the dialog for adding a new database connection when selected.
</p>
<h5>Drag and drop support for database objects</h5>
<p>
A component might need to allow database tables from the Database Explorer to
be dragged to a visual editor. An API is provided in <code>DatabaseMetaDataTransfer</code>
containing <code>DataFlavor</code>s for database objects and nested classes
encapsulating those database objects during a drag and drop transfer.
</p>
<h5>Get support for working with SQL identifiers</h5>
<p>
A component might need support for working with SQL identifiers. In particular,
it's important to know when to quote a SQL identifier. The
<a href="org/netbeans/api/db/sql/support/SQLIdentifiers.Quoter.html" shape="rect">
SQLIdentifiers.Quoter</a> class is provided for this.
</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>DatabaseExplorerAPI</td><td>Exported</td><td><a href="http://wiki.netbeans.org/API_Stability#Official">Official</a></td><td><a name="java-DatabaseExplorerAPI"><a href="index.html">index.html</a>
<p></p>
</a></td>
</tr>
<tr class="tabler">
<td>SQLSupportAPI</td><td>Exported</td><td><a href="http://wiki.netbeans.org/API_Stability#Official">Official</a></td><td><a name="java-SQLSupportAPI"><a href="org/netbeans/api/db/sql/support/package-summary.html">
.../api/db/sql/support/package-summary.html</a>
<p></p>
</a></td>
</tr>
</table>
</td>
</tr>
</table>
<p></p>
<a name="group-layer">
<h5>Group of layer 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>DatabaseExplorerLayerAPI</td><td>Exported</td><td><a href="http://wiki.netbeans.org/API_Stability#Official">Official</a></td><td><a name="layer-DatabaseExplorerLayerAPI"><a href="index.html">index.html</a>
<p></p>
</a></td>
</tr>
<tr class="tabler">
<td>Loaders-text-dbschema-Actions</td><td>Exported</td><td><a href="http://wiki.netbeans.org/API_Stability#Devel">Under Development</a></td><td><a name="layer-Loaders-text-dbschema-Actions"><a href="index.html">index.html</a>
<p></p>
</a></td>
</tr>
<tr class="tabler">
<td>Loaders-text-sql-Actions</td><td>Exported</td><td><a href="http://wiki.netbeans.org/API_Stability#Devel">Under Development</a></td><td><a name="layer-Loaders-text-sql-Actions"><a href="index.html">index.html</a>
<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>
<p>
Nothing.
</p>
<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.db/1 1.68.1 30</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>