Browse Source

Revise contribution

See gh-36022
pull/35344/merge
Sam Brannen 4 days ago
parent
commit
452257eb96
  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/aot-cache.adoc
  4. 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 @@ -6,7 +6,7 @@ are set by using the `setVariable()` method in `EvaluationContext` implementatio
[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.
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. @@ -349,11 +349,11 @@ parameters return the data read from the table.
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
layer. Compared to the `StoredProcedure` class, you need not create a subclass
and you need not declare parameters that can be looked up in the database metadata.
The following example of a `SimpleJdbcCall` configuration uses the preceding stored
procedure (the only configuration option, in addition to the `DataSource`, is the name
of the stored procedure):
layer. In contrast to the `StoredProcedure` class, you do not need to create a subclass,
and you do not need to declare parameters that can be looked up in the database metadata.
The following `SimpleJdbcCall` configuration example uses the preceding stored procedure.
The only configuration option (other than the `DataSource`) is the name of the stored
procedure.
[tabs]
======

2
framework-docs/modules/ROOT/pages/integration/aot-cache.adoc

@ -7,7 +7,7 @@ The ahead-of-time cache is a JVM feature introduced in Java 24 via the @@ -7,7 +7,7 @@ The ahead-of-time cache is a JVM feature introduced in Java 24 via the
https://openjdk.org/jeps/483[JEP 483] that can help reduce the startup time and memory
footprint of Java applications. AOT cache is a natural evolution of https://docs.oracle.com/en/java/javase/17/vm/class-data-sharing.html[Class Data Sharing (CDS)].
Spring Framework supports both CDS and AOT cache, and it is recommended that you use the
later if available in the JVM version you are using (Java 24+).
latter if available in the JVM version you are using (Java 24+).
To use this feature, an AOT cache should be created for the particular classpath of the
application. It is possible to create this cache on the deployed instance, or during a

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

@ -313,7 +313,7 @@ xref:integration/jmx/naming.adoc#jmx-context-mbeanexport[Configuring Annotation- @@ -313,7 +313,7 @@ xref:integration/jmx/naming.adoc#jmx-context-mbeanexport[Configuring Annotation-
=== The `cache` Schema
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/declarative-xml.adoc[Declarative XML-based Caching] for details.

Loading…
Cancel
Save