parent
360f555e77
commit
a2e5d9a14f
|
@ -88,7 +88,7 @@ public abstract class SpringBeanAutowiringSupport {
|
|||
if (logger.isWarnEnabled()) {
|
||||
logger.warn("Current WebApplicationContext is not available for processing of " +
|
||||
ClassUtils.getShortName(target.getClass()) + ": " +
|
||||
"Make sure this class gets constructed in a Spring web application after the" +
|
||||
"Make sure this class gets constructed in a Spring web application after the " +
|
||||
"Spring WebApplicationContext has been initialized. Proceeding without injection.");
|
||||
}
|
||||
}
|
||||
|
|
|
@ -2054,7 +2054,7 @@ and others) and is equivalent to `required=false`.
|
|||
| Currently authenticated user -- possibly a specific `Principal` implementation class if known.
|
||||
|
||||
Note that this argument is not resolved eagerly, if it is annotated in order to allow a custom resolver to resolve it
|
||||
before falling back on default resolution resolution via `HttpServletRequest#getUserPrincipal`.
|
||||
before falling back on default resolution via `HttpServletRequest#getUserPrincipal`.
|
||||
For example, the Spring Security `Authentication` implements `Principal` and would be injected as such via
|
||||
`HttpServletRequest#getUserPrincipal`, unless it is also annotated with `@AuthenticationPrincipal` in which case it
|
||||
is resolved by a custom Spring Security resolver through `Authentication#getPrincipal`.
|
||||
|
|
Loading…
Reference in New Issue