mirror of
https://github.com/spring-projects/spring-boot.git
synced 2024-08-29 03:06:45 +08:00
Fix javax with jakarta references in documentation
This commit is contained in:
parent
3b6b795c9f
commit
1e70822adb
@ -1137,7 +1137,7 @@ Doing so gives a transparent upgrade path while supporting a much richer format.
|
||||
[[features.external-config.typesafe-configuration-properties.validation]]
|
||||
==== @ConfigurationProperties Validation
|
||||
Spring Boot attempts to validate `@ConfigurationProperties` classes whenever they are annotated with Spring's `@Validated` annotation.
|
||||
You can use JSR-303 `javax.validation` constraint annotations directly on your configuration class.
|
||||
You can use JSR-303 `jakarta.validation` constraint annotations directly on your configuration class.
|
||||
To do so, ensure that a compliant JSR-303 implementation is on your classpath and then add constraint annotations to your fields, as shown in the following example:
|
||||
|
||||
include::code:MyProperties[]
|
||||
|
@ -1,7 +1,7 @@
|
||||
[[io.validation]]
|
||||
== Validation
|
||||
The method validation feature supported by Bean Validation 1.1 is automatically enabled as long as a JSR-303 implementation (such as Hibernate validator) is on the classpath.
|
||||
This lets bean methods be annotated with `javax.validation` constraints on their parameters and/or on their return value.
|
||||
This lets bean methods be annotated with `jakarta.validation` constraints on their parameters and/or on their return value.
|
||||
Target classes with such annotated methods need to be annotated with the `@Validated` annotation at the type level for their methods to be searched for inline constraint annotations.
|
||||
|
||||
For instance, the following service triggers the validation of the first argument, making sure its size is between 8 and 10:
|
||||
@ -13,4 +13,4 @@ This allows you to use <<features.adoc#features.internationalization,your applic
|
||||
Once the parameters have been resolved, message interpolation is completed using Bean Validation's default interpolator.
|
||||
|
||||
To customize the `Configuration` used to build the `ValidatorFactory`, define a `ValidationConfigurationCustomizer` bean.
|
||||
When multiple customizer beans are defined, they are called in order based on their `@Order` annotation or `Ordered` implementation.
|
||||
When multiple customizer beans are defined, they are called in order based on their `@Order` annotation or `Ordered` implementation.
|
||||
|
@ -1,6 +1,6 @@
|
||||
[[messaging.jms]]
|
||||
== JMS
|
||||
The `javax.jms.ConnectionFactory` interface provides a standard method of creating a `javax.jms.Connection` for interacting with a JMS broker.
|
||||
The `jakarta.jms.ConnectionFactory` interface provides a standard method of creating a `jakarta.jms.Connection` for interacting with a JMS broker.
|
||||
Although Spring needs a `ConnectionFactory` to work with JMS, you generally need not use it directly yourself and can instead rely on higher level messaging abstractions.
|
||||
(See the {spring-framework-docs}/integration.html#jms[relevant section] of the Spring Framework reference documentation for details.)
|
||||
Spring Boot also auto-configures the necessary infrastructure to send and receive messages.
|
||||
@ -88,9 +88,10 @@ If a `DestinationResolver` or a `MessageConverter` bean is defined, it is associ
|
||||
|
||||
[[messaging.jms.receiving]]
|
||||
=== Receiving a Message
|
||||
|
||||
When the JMS infrastructure is present, any bean can be annotated with `@JmsListener` to create a listener endpoint.
|
||||
If no `JmsListenerContainerFactory` has been defined, a default one is configured automatically.
|
||||
If a `DestinationResolver`, a `MessageConverter`, or a `javax.jms.ExceptionListener` beans are defined, they are associated automatically with the default factory.
|
||||
If a `DestinationResolver`, a `MessageConverter`, or a `jakarta.jms.ExceptionListener` beans are defined, they are associated automatically with the default factory.
|
||||
|
||||
By default, the default factory is transactional.
|
||||
If you run in an infrastructure where a `JtaTransactionManager` is present, it is associated to the listener container by default.
|
||||
|
@ -10,7 +10,7 @@ WebSocket support is also available for {spring-framework-docs}/web-reactive.htm
|
||||
[source,xml,indent=0,subs="verbatim"]
|
||||
----
|
||||
<dependency>
|
||||
<groupId>javax.websocket</groupId>
|
||||
<artifactId>javax.websocket-api</artifactId>
|
||||
<groupId>jakarta.websocket</groupId>
|
||||
<artifactId>jakarta.websocket-api</artifactId>
|
||||
</dependency>
|
||||
----
|
||||
|
Loading…
Reference in New Issue
Block a user