FailureAnalysis class final
A plain-language explanation of why the application failed to start, with what to do about it.
A start that fails deep in bean creation produces a long chain of
wrapped exceptions. Instead of the stack trace, SpringApplication
prints an APPLICATION FAILED TO START report built from one of these:
a description of the problem and an action to fix it. The built-in
analysis covers missing and ambiguous beans, dependency cycles,
unresolved placeholders, duplicate bean names, missing config files and
invalid properties. A FailureAnalyzer returns one for errors of your
own.
Spring (Java): FailureAnalysis, with the same three parts.
Constructors
- FailureAnalysis(String description, String action, Object cause)
-
An analysis that explains
causewithdescriptionand suggestsaction.const
Properties
- action → String
-
What the developer should do to fix it.
final
- cause → Object
-
The error that was analyzed.
final
- description → String
-
What went wrong, in terms of the application (the bean, property or
file involved). It may span several lines.
final
- hashCode → int
-
The hash code for this object.
no setterinherited
- report → String
-
The whole report as it is printed when the start fails, with the
description and action filled in:
no setter
- runtimeType → Type
-
A representation of the runtime type of the object.
no setterinherited
Methods
-
noSuchMethod(
Invocation invocation) → dynamic -
Invoked when a nonexistent method or property is accessed.
inherited
-
toString(
) → String -
A string representation of this object.
inherited
Operators
-
operator ==(
Object other) → bool -
The equality operator.
inherited