Browse Source

Revise contribution

See gh-36022

(cherry picked from commit 452257eb96)
6.2.x
Sam Brannen 5 days ago
parent
commit
836289315d
  1. 2
      framework-docs/modules/ROOT/pages/core/expressions/language-ref/variables.adoc
  2. 10
      framework-docs/modules/ROOT/pages/data-access/jdbc/simple.adoc
  3. 2
      framework-docs/modules/ROOT/pages/integration/appendix.adoc

2
framework-docs/modules/ROOT/pages/core/expressions/language-ref/variables.adoc

@ -6,7 +6,7 @@ are set by using the `setVariable()` method in `EvaluationContext` implementatio
[NOTE] [NOTE]
==== ====
Variable names must be begun with a letter (as defined below), an underscore, or a dollar Variable names must begin with a letter (as defined below), an underscore, or a dollar
sign. sign.
Variable names must be composed of one or more of the following supported types of Variable names must be composed of one or more of the following supported types of

10
framework-docs/modules/ROOT/pages/data-access/jdbc/simple.adoc

@ -349,11 +349,11 @@ parameters return the data read from the table.
You can declare `SimpleJdbcCall` in a manner similar to declaring `SimpleJdbcInsert`. You You can declare `SimpleJdbcCall` in a manner similar to declaring `SimpleJdbcInsert`. You
should instantiate and configure the class in the initialization method of your data-access should instantiate and configure the class in the initialization method of your data-access
layer. Compared to the `StoredProcedure` class, you need not create a subclass layer. In contrast to the `StoredProcedure` class, you do not need to create a subclass,
and you need not declare parameters that can be looked up in the database metadata. and you do not need to declare parameters that can be looked up in the database metadata.
The following example of a `SimpleJdbcCall` configuration uses the preceding stored The following `SimpleJdbcCall` configuration example uses the preceding stored procedure.
procedure (the only configuration option, in addition to the `DataSource`, is the name The only configuration option (other than the `DataSource`) is the name of the stored
of the stored procedure): procedure.
[tabs] [tabs]
====== ======

2
framework-docs/modules/ROOT/pages/integration/appendix.adoc

@ -313,7 +313,7 @@ xref:integration/jmx/naming.adoc#jmx-context-mbeanexport[Configuring Annotation-
=== The `cache` Schema === The `cache` Schema
You can use the `cache` elements to enable support for Spring's `@CacheEvict`, `@CachePut`, You can use the `cache` elements to enable support for Spring's `@CacheEvict`, `@CachePut`,
and `@Caching` annotations. It is also supports declarative XML-based caching. See and `@Caching` annotations. The `cache` schema also supports declarative XML-based caching. See
xref:integration/cache/annotations.adoc#cache-annotation-enable[Enabling Caching Annotations] and xref:integration/cache/annotations.adoc#cache-annotation-enable[Enabling Caching Annotations] and
xref:integration/cache/declarative-xml.adoc[Declarative XML-based Caching] for details. xref:integration/cache/declarative-xml.adoc[Declarative XML-based Caching] for details.

Loading…
Cancel
Save