From c6fa690d2e2e20b0ef671e1c533d138bde7de72e Mon Sep 17 00:00:00 2001 From: Luke Taylor Date: Mon, 24 Aug 2009 11:40:28 +0000 Subject: [PATCH] Fixed some docbook links --- docs/manual/src/docbook/appendix-namespace.xml | 4 ++-- docs/manual/src/docbook/core-filters.xml | 9 ++++----- 2 files changed, 6 insertions(+), 7 deletions(-) diff --git a/docs/manual/src/docbook/appendix-namespace.xml b/docs/manual/src/docbook/appendix-namespace.xml index 6732d7ce5c..85cb02a2ac 100644 --- a/docs/manual/src/docbook/appendix-namespace.xml +++ b/docs/manual/src/docbook/appendix-namespace.xml @@ -124,8 +124,8 @@ default AccessDeniedHandler used by the ExceptionTranslationFilter, (using the error-page attribute, or to supply your own implementation using the - ref attribute. See for more - information on the implementation details. + ref attribute. This is discussed in more detail in the section on + the ExceptionTranslationFilter.
The <literal><intercept-url></literal> Element diff --git a/docs/manual/src/docbook/core-filters.xml b/docs/manual/src/docbook/core-filters.xml index 6f6892d653..b74ab3f5e1 100644 --- a/docs/manual/src/docbook/core-filters.xml +++ b/docs/manual/src/docbook/core-filters.xml @@ -8,8 +8,7 @@
<classname>FilterSecurityInterceptor</classname> We've already seen FilterSecurityInterceptor briefly when - discussing access-control in general (see), and we've already used it with the namespace where the + discussing access-control in general, and we've already used it with the namespace where the <intercept-url> elements are combined to configure it internally. Now we'll see how to explicitly configure it for use with a FilterChainProxy, along with its companion filter @@ -31,7 +30,7 @@ AuthenticationManager and an AccessDecisionManager. It is also supplied with configuration attributes that apply to different HTTP URL requests. Refer back to where we saw these originally. + xlink:href="#tech-intro-config-attributes">the original discussion on these in the technical introduction. The FilterSecurityInterceptor can be configured with configuration attributes in two ways. The first, which is shown above, is using the <filter-security-metadata-source> namespace element. This @@ -166,8 +165,8 @@ can implement the interface yourself and use your own implementation. It's also possible to supply a custom AccessDeniedHandler when you're using the - namespace to configure your application. See . + namespace to configure your application. See + the namespace appendix for more details.
<classname>SecurityContextPersistenceFilter</classname>