Skip to content

Commit bc0e59f

Browse files
Anders D. Johnsonsnicoll
Anders D. Johnson
authored andcommitted
Fix condition vs. conditional typo in documenation
Issue: SPR-12273
1 parent a3fd00e commit bc0e59f

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

src/asciidoc/index.adoc

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -49227,7 +49227,7 @@ result in an exception as a custom `CacheManager` will be ignored by the
4922749227
===== Conditional caching
4922849228
Sometimes, a method might not be suitable for caching all the time (for example, it
4922949229
might depend on the given arguments). The cache annotations support such functionality
49230-
through the `conditional` parameter which takes a `SpEL` expression that is evaluated to
49230+
through the `condition` parameter which takes a `SpEL` expression that is evaluated to
4923149231
either `true` or `false`. If `true`, the method is cached - if not, it behaves as if the
4923249232
method is not cached, that is executed every since time no matter what values are in the
4923349233
cache or what arguments are used. A quick example - the following method will be cached
@@ -49240,8 +49240,8 @@ only if the argument `name` has a length shorter than 32:
4924049240
public Book findBook(String name)
4924149241
----
4924249242

49243-
In addition the `conditional` parameter, the `unless` parameter can be used to veto the
49244-
adding of a value to the cache. Unlike `conditional`, `unless` expressions are evaluated
49243+
In addition the `condition` parameter, the `unless` parameter can be used to veto the
49244+
adding of a value to the cache. Unlike `condition`, `unless` expressions are evaluated
4924549245
__after__ the method has been called. Expanding on the previous example - perhaps we
4924649246
only want to cache paperback books:
4924749247

0 commit comments

Comments
 (0)