Fixed ambiguous sentence in conditional cache documentation

Issue: SPR-14399
This commit is contained in:
Juergen Hoeller 2016-06-26 00:13:53 +02:00
parent 351a729317
commit 4102c62734
1 changed files with 3 additions and 3 deletions

View File

@ -8436,9 +8436,9 @@ Sometimes, a method might not be suitable for caching all the time (for example,
might depend on the given arguments). The cache annotations support such functionality might depend on the given arguments). The cache annotations support such functionality
through the `condition` parameter which takes a `SpEL` expression that is evaluated to through the `condition` parameter which takes a `SpEL` expression that is evaluated to
either `true` or `false`. If `true`, the method is cached - if not, it behaves as if the either `true` or `false`. If `true`, the method is cached - if not, it behaves as if the
method is not cached, that is executed every since time no matter what values are in the method is not cached, that is executed every time no matter what values are in the cache
cache or what arguments are used. A quick example - the following method will be cached or what arguments are used. A quick example - the following method will be cached only
only if the argument `name` has a length shorter than 32: if the argument `name` has a length shorter than 32:
[source,java,indent=0] [source,java,indent=0]
[subs="verbatim,quotes"] [subs="verbatim,quotes"]