Link to API docs.
git-svn-id: https://svn.apache.org/repos/asf/xml/commons/trunk@226084 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
parent
5addd1f72d
commit
cf79971545
@ -164,7 +164,7 @@ to perform entity resolution. Many users will want to simply use
|
||||
these classes directly <quote>out of the box</quote> with their applications
|
||||
(such as Xalan and Saxon), but developers may also be interested in
|
||||
the
|
||||
<ulink url="apidocs/index.html" role="linktable" xreflabel="JavaDoc API Documentation">JavaDoc
|
||||
<ulink url="../apidocs/resolver/index.html" role="linktable" xreflabel="JavaDoc API Documentation">JavaDoc
|
||||
API Documentation</ulink>.
|
||||
</para>
|
||||
|
||||
@ -800,7 +800,7 @@ in <xref linkend="ex1"/> demonstrates how straightforward this is:</para>
|
||||
<filename>CatalogManager.properties</filename> file on your
|
||||
<envar>CLASSPATH</envar>.
|
||||
(For all the
|
||||
gory details about these classes, consult <ulink url="apidocs/index.html">the
|
||||
gory details about these classes, consult <ulink url="../apidocs/resolver/index.html">the
|
||||
API documentation</ulink>.) You can explicitly parse your own catalogs (perhaps
|
||||
taken from command line arguments or a Preferences dialog) instead of or in
|
||||
addition to the system catalogs.</para>
|
||||
|
||||
@ -14,9 +14,11 @@
|
||||
<overview label="Overview" href="index.html"/>
|
||||
<article label="Article" href="resolver-article.html"/>
|
||||
<release-notes label="Release Notes" href="resolver-release-notes.html"/>
|
||||
<apidocs label="API docs" href="../apidocs/resolver/index.html"/>
|
||||
</resolver>
|
||||
<which label="Which" href="which/">
|
||||
<overview label="Overview" href="index.html"/>
|
||||
<apidocs label="API docs" href="../apidocs/which/index.html"/>
|
||||
</which>
|
||||
<external label="External" href="external/">
|
||||
<overview label="Overview" href="index.html"/>
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user