You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@directory.apache.org by gi...@apache.org on 2022/07/25 17:20:39 UTC
[directory-site] branch asf-site updated: Updated site from master (1ec2da451a0c6466311c82886c19509aed41cdaf)
This is an automated email from the ASF dual-hosted git repository.
git-site-role pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/directory-site.git
The following commit(s) were added to refs/heads/asf-site by this push:
new a4bd81df Updated site from master (1ec2da451a0c6466311c82886c19509aed41cdaf)
a4bd81df is described below
commit a4bd81dfee27da4c29ab7522446e3252820ab366
Author: jenkins <bu...@apache.org>
AuthorDate: Mon Jul 25 17:20:34 2022 +0000
Updated site from master (1ec2da451a0c6466311c82886c19509aed41cdaf)
---
content/fortress/exception-handling.html | 55 ++++++++++++++++----------------
content/fortress/index.xml | 4 +--
content/index.xml | 4 +--
content/sitemap.xml | 4 +--
4 files changed, 34 insertions(+), 33 deletions(-)
diff --git a/content/fortress/exception-handling.html b/content/fortress/exception-handling.html
index 830fde0a..06997c3a 100644
--- a/content/fortress/exception-handling.html
+++ b/content/fortress/exception-handling.html
@@ -131,9 +131,9 @@
<h1 id="fortress-exception-handling">Fortress Exception Handling</h1>
-<p>Fortress communicates errors to the user through checked exceptions. At the highest level, is the <a href="https://directory.apache.org/fortress/gen-docs/latest/apidocs/org/apache/directory/fortress/core/SecurityException.html">SecurityException</a></p>
-<p>The SecurityException is declared to be thrown by all APIs within Fortress Manager interfaces.
-The original exception thrown may be of this type or one of its extensions</p>
+<p>Fortress communicates errors to the caller via checked exceptions. At the highest level is the <a href="https://directory.apache.org/fortress/gen-docs/latest/apidocs/org/apache/directory/fortress/core/SecurityException.html">SecurityException</a>.</p>
+<p>It is declared to be thrown by all APIs within the Fortress Manager interfaces.
+The original exception thrown may be of this type or one of its extensions:</p>
<ul>
<li><a href="https://directory.apache.org/fortress/gen-docs/latest/apidocs/org/apache/directory/fortress/core/AuthorizationException.html">AuthorizationException</a> in the event user fails administrative permission check.</li>
<li><a href="https://directory.apache.org/fortress/gen-docs/latest/apidocs/org/apache/directory/fortress/core/CfgException.html">CfgException</a> in the event the runtime cfg system fails.</li>
@@ -145,8 +145,9 @@ The original exception thrown may be of this type or one of its extensions</p>
<li><a href="https://directory.apache.org/fortress/gen-docs/latest/apidocs/org/apache/directory/fortress/core/UpdateException.html">UpdateException</a> in the event DAO cannot update entity.</li>
<li><a href="https://directory.apache.org/fortress/gen-docs/latest/apidocs/org/apache/directory/fortress/core/ValidationException.html">ValidationException</a> in the event entity validation fails.</li>
</ul>
-<p>For certain methods like AccessMgr.createSession, or AccessMgr.authenticate, the caller may need to differentiate by one of the above subclasses, e.g. PasswordException, to facilitate password expiring condition or allow user to retry authentication after entering it incorrectly. If specific exception processing is not the aim, or if differentiating conditions by SecurityException#errorId is acceptable, callers are allowed to catch (or throw) as type SecurityException.</p>
-<p>All exceptions generated by Fortress will be set with error code BaseException.getErrorId() indicating fault condition which is set via its constructor. The error codes are declared in <a href="https://directory.apache.org/fortress/gen-docs/latest/apidocs/org/apache/directory/fortress/core/GlobalErrIds.html">GlobalErrIds</a> and are also listed below:</p>
+<p>For some methods, e.g. AccessMgr.createSession, AccessMgr.authenticate, the caller may need to differentiate by one of the above subclasses, e.g. PasswordException, to facilitate password expiring condition or allow user to retry authentication after entering it incorrectly.
+If specific exception processing is not required and differentiating conditions by SecurityException#errorId is acceptable, callers are allowed to catch (or throw) as type SecurityException.</p>
+<p>All exceptions generated by Fortress will be set as an error code. These codes are declared in <a href="https://directory.apache.org/fortress/gen-docs/latest/apidocs/org/apache/directory/fortress/core/GlobalErrIds.html">GlobalErrIds</a> and are also listed below:</p>
<table>
<thead>
<tr>
@@ -184,7 +185,7 @@ The original exception thrown may be of this type or one of its extensions</p>
<tr>
<td>107</td>
<td>FT_CONFIG_NOT_FOUND</td>
-<td>The remote cfg instance could not be found on the ldap server.</td>
+<td>The remote cfg instance could not be found on the server.</td>
</tr>
<tr>
<td>108</td>
@@ -209,27 +210,27 @@ The original exception thrown may be of this type or one of its extensions</p>
<tr>
<td>120</td>
<td>FT_CONFIG_CREATE_FAILED</td>
-<td>The config node could not be created on ldap server.</td>
+<td>The config node could not be created on server.</td>
</tr>
<tr>
<td>121</td>
<td>FT_CONFIG_UPDATE_FAILED</td>
-<td>The config node could not be updated on ldap server.</td>
+<td>The config node could not be updated on server.</td>
</tr>
<tr>
<td>122</td>
<td>FT_CONFIG_DELETE_FAILED</td>
-<td>The config node could not be removed from ldap.</td>
+<td>The config node could not be removed from server.</td>
</tr>
<tr>
<td>123</td>
<td>FT_CONFIG_DELETE_PROPS_FAILED</td>
-<td>The config parameters could not be removed from ldap.</td>
+<td>The config parameters could not be removed from server.</td>
</tr>
<tr>
<td>124</td>
<td>FT_CONFIG_READ_FAILED</td>
-<td>The config node could not be read from ldap.</td>
+<td>The config node could not be read from server.</td>
</tr>
<tr>
<td>125</td>
@@ -239,12 +240,12 @@ The original exception thrown may be of this type or one of its extensions</p>
<tr>
<td>126</td>
<td>FT_CONFIG_BOOTSTRAP_FAILED</td>
-<td>The config node could not be read from ldap.</td>
+<td>The config node could not be read from server.</td>
</tr>
<tr>
<td>127</td>
<td>FT_CONFIG_INITIALIZE_FAILED</td>
-<td>The config node could not be read from ldap.</td>
+<td>The config node could not be read from server.</td>
</tr>
<tr>
<td>128</td>
@@ -294,32 +295,32 @@ The original exception thrown may be of this type or one of its extensions</p>
<tr>
<td>1000</td>
<td>USER_SEARCH_FAILED</td>
-<td>The User node could not be searched in ldap.</td>
+<td>The User node could not be searched on server.</td>
</tr>
<tr>
<td>1001</td>
<td>USER_READ_FAILED</td>
-<td>The User node could not be read from ldap.</td>
+<td>The User node could not be read from server.</td>
</tr>
<tr>
<td>1002</td>
<td>USER_ADD_FAILED</td>
-<td>The User node could not be added to ldap.</td>
+<td>The User node could not be added to server.</td>
</tr>
<tr>
<td>1003</td>
<td>USER_UPDATE_FAILED</td>
-<td>The User node could not be updated in ldap.</td>
+<td>The User node could not be updated on server.</td>
</tr>
<tr>
<td>1004</td>
<td>USER_DELETE_FAILED</td>
-<td>The User node could not be deleted from ldap.</td>
+<td>The User node could not be deleted from server.</td>
</tr>
<tr>
<td>1005</td>
<td>USER_NOT_FOUND</td>
-<td>The User node was not found in ldap.</td>
+<td>The User node was not found on server.</td>
</tr>
<tr>
<td>1006</td>
@@ -329,7 +330,7 @@ The original exception thrown may be of this type or one of its extensions</p>
<tr>
<td>1007</td>
<td>USER_ID_DUPLICATE</td>
-<td>The User could not be added because it already exists in ldap.</td>
+<td>The User could not be added because it already exists.</td>
</tr>
<tr>
<td>1008</td>
@@ -354,7 +355,7 @@ The original exception thrown may be of this type or one of its extensions</p>
<tr>
<td>1012</td>
<td>USER_PW_PLCY_DEL_FAILED</td>
-<td>The PW Policy node could not be removed from ldap.</td>
+<td>The PW Policy node could not be removed from server.</td>
</tr>
<tr>
<td>1013</td>
@@ -364,7 +365,7 @@ The original exception thrown may be of this type or one of its extensions</p>
<tr>
<td>1014</td>
<td>USER_PW_CHK_FAILED</td>
-<td>The User password check failed in ldap.</td>
+<td>The User password check failed on server.</td>
</tr>
<tr>
<td>1015</td>
@@ -484,7 +485,7 @@ The original exception thrown may be of this type or one of its extensions</p>
<tr>
<td>1038</td>
<td>USER_ADD_FAILED_ALREADY_EXISTS</td>
-<td>The User node could not be added to ldap.</td>
+<td>The User node could not be added to server.</td>
</tr>
<tr>
<td>1039</td>
@@ -659,7 +660,7 @@ The original exception thrown may be of this type or one of its extensions</p>
<tr>
<td>3007</td>
<td>PERM_OBJ_NOT_FOUND</td>
-<td>The supplied Permission object could not be found on ldap server.</td>
+<td>The supplied Permission object could not be found on server.</td>
</tr>
<tr>
<td>3008</td>
@@ -1349,7 +1350,7 @@ The original exception thrown may be of this type or one of its extensions</p>
<tr>
<td>8021</td>
<td>ORG_REMOVE_PARENT_FAILED_USER</td>
-<td>The supplied Perm OU entity parent attribute could not be updated due to ldap error.</td>
+<td>The supplied Perm OU entity parent attribute could not be updated due to error on server.</td>
</tr>
<tr>
<td>8061</td>
@@ -1564,7 +1565,7 @@ The original exception thrown may be of this type or one of its extensions</p>
<tr>
<td>9028</td>
<td>ARLE_REMOVE_PARENT_FAILED</td>
-<td>The supplied Administrative Role parent attribute could not be removed on ldap server.</td>
+<td>The supplied Administrative Role parent attribute could not be removed on server.</td>
</tr>
<tr>
<td>9029</td>
@@ -1839,7 +1840,7 @@ The original exception thrown may be of this type or one of its extensions</p>
<tr>
<td>10503</td>
<td>ENTITY_PROPS_LOAD_FAILED</td>
-<td>The entity was not found</td>
+<td>The entity was not found.</td>
</tr>
</tbody>
</table>
diff --git a/content/fortress/index.xml b/content/fortress/index.xml
index 5d8d86ba..b68cf31c 100644
--- a/content/fortress/index.xml
+++ b/content/fortress/index.xml
@@ -213,8 +213,8 @@ Use cases supported Create, Read, Update, Delete policies Testing of policies
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://directory.apache.org/fortress/exception-handling.html</guid>
- <description>Fortress Exception Handling Fortress communicates errors to the user through checked exceptions. At the highest level, is the SecurityException
-The SecurityException is declared to be thrown by all APIs within Fortress Manager interfaces. The original exception thrown may be of this type or one of its extensions
+ <description>Fortress Exception Handling Fortress communicates errors to the caller via checked exceptions. At the highest level is the SecurityException.
+It is declared to be thrown by all APIs within the Fortress Manager interfaces. The original exception thrown may be of this type or one of its extensions:
AuthorizationException in the event user fails administrative permission check. CfgException in the event the runtime cfg system fails. CreateException in the event DAO cannot create entity.</description>
</item>
diff --git a/content/index.xml b/content/index.xml
index 926e0cae..75e29a26 100644
--- a/content/index.xml
+++ b/content/index.xml
@@ -3535,8 +3535,8 @@ Apache Directory Studio RCP Application Apache Directory Studio is a multi-platf
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://directory.apache.org/fortress/exception-handling.html</guid>
- <description>Fortress Exception Handling Fortress communicates errors to the user through checked exceptions. At the highest level, is the SecurityException
-The SecurityException is declared to be thrown by all APIs within Fortress Manager interfaces. The original exception thrown may be of this type or one of its extensions
+ <description>Fortress Exception Handling Fortress communicates errors to the caller via checked exceptions. At the highest level is the SecurityException.
+It is declared to be thrown by all APIs within the Fortress Manager interfaces. The original exception thrown may be of this type or one of its extensions:
AuthorizationException in the event user fails administrative permission check. CfgException in the event the runtime cfg system fails. CreateException in the event DAO cannot create entity.</description>
</item>
diff --git a/content/sitemap.xml b/content/sitemap.xml
index 2aca5794..19651e93 100644
--- a/content/sitemap.xml
+++ b/content/sitemap.xml
@@ -1754,7 +1754,7 @@
<url>
<loc>https://directory.apache.org/fortress/exception-handling.html</loc>
- <lastmod>2022-07-25T11:46:39-05:00</lastmod>
+ <lastmod>2022-07-25T12:18:33-05:00</lastmod>
</url>
<url>
@@ -1799,7 +1799,7 @@
<url>
<loc>https://directory.apache.org/fortress.html</loc>
- <lastmod>2022-07-25T11:46:39-05:00</lastmod>
+ <lastmod>2022-07-25T12:18:33-05:00</lastmod>
</url>
<url>