Cwikius-Spring
/
spring-security
mirror of https://github.com/spring-projects/spring-security.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

SEC-3124: Fix broken Javadoc related to `<` and `>`

This commit is contained in:
izeye 2015-10-10 16:59:11 +09:00 committed by Rob Winch
parent 81d61c2715
commit 3925ed90c4
2 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
web/src/main/java/org/springframework/security/web/FilterChainProxy.java
View File

@ -41,7 +41,7 @@ import java.util.*;
* version 2.0, you shouldn't need to explicitly configure a {@code FilterChainProxy} bean * version 2.0, you shouldn't need to explicitly configure a {@code FilterChainProxy} bean
* in your application context unless you need very fine control over the filter chain * in your application context unless you need very fine control over the filter chain
* contents. Most cases should be adequately covered by the default * contents. Most cases should be adequately covered by the default
* {@code &lt;security:http /&gt;} namespace configuration options. * {@code <security:http />} namespace configuration options.
* <p> * <p>
* The {@code FilterChainProxy} is linked into the servlet container filter chain by * The {@code FilterChainProxy} is linked into the servlet container filter chain by
* adding a standard Spring {@link DelegatingFilterProxy} declaration in the application * adding a standard Spring {@link DelegatingFilterProxy} declaration in the application
@ -54,7 +54,7 @@ import java.util.*;
* and a list of filters which should be applied to matching requests. Most applications * and a list of filters which should be applied to matching requests. Most applications
* will only contain a single filter chain, and if you are using the namespace, you don't * will only contain a single filter chain, and if you are using the namespace, you don't
* have to set the chains explicitly. If you require finer-grained control, you can make * have to set the chains explicitly. If you require finer-grained control, you can make
* use of the {@code &lt;filter-chain&gt;} namespace element. This defines a URI pattern * use of the {@code <filter-chain>} namespace element. This defines a URI pattern
* and the list of filters (as comma-separated bean names) which should be applied to * and the list of filters (as comma-separated bean names) which should be applied to
* requests which match the pattern. An example configuration might look like this: * requests which match the pattern. An example configuration might look like this:
* *

2
web/src/main/java/org/springframework/security/web/access/intercept/DefaultFilterInvocationSecurityMetadataSource.java
View File

@ -43,7 +43,7 @@ import org.springframework.security.web.util.matcher.RequestMatcher;
* <p> * <p>
* The most common method creating an instance is using the Spring Security namespace. For * The most common method creating an instance is using the Spring Security namespace. For
* example, the {@code pattern} and {@code access} attributes of the * example, the {@code pattern} and {@code access} attributes of the
* {@code &lt;intercept-url&gt;} elements defined as children of the {@code &lt;http&gt;} * {@code <intercept-url>} elements defined as children of the {@code <http>}
* element are combined to build the instance used by the * element are combined to build the instance used by the
* {@code FilterSecurityInterceptor}. * {@code FilterSecurityInterceptor}.
* *