|
|
|
@ -445,8 +445,8 @@ through Java 8's `java.util.Optional`, as the following example shows: |
|
|
|
---- |
|
|
|
---- |
|
|
|
|
|
|
|
|
|
|
|
You can also use a parameter-level `@Nullable` annotation (of any kind in any package -- |
|
|
|
You can also use a parameter-level `@Nullable` annotation (of any kind in any package -- |
|
|
|
for example, `javax.annotation.Nullable` from JSR-305) or just leverage Kotlin built-in |
|
|
|
for example, `org.jspecify.annotations.Nullable` from JSpecify) or just leverage Kotlin's |
|
|
|
null-safety support: |
|
|
|
built-in null-safety support: |
|
|
|
|
|
|
|
|
|
|
|
[tabs] |
|
|
|
[tabs] |
|
|
|
====== |
|
|
|
====== |
|
|
|
@ -477,13 +477,6 @@ Kotlin:: |
|
|
|
---- |
|
|
|
---- |
|
|
|
====== |
|
|
|
====== |
|
|
|
|
|
|
|
|
|
|
|
[NOTE] |
|
|
|
|
|
|
|
==== |
|
|
|
|
|
|
|
A type-level `@Nullable` annotation such as from JSpecify is not supported in Spring |
|
|
|
|
|
|
|
Framework 6.2 yet. You need to upgrade to Spring Framework 7.0 where the framework |
|
|
|
|
|
|
|
detects type-level annotations and consistently declares JSpecify in its own codebase. |
|
|
|
|
|
|
|
==== |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
You can also use `@Autowired` for interfaces that are well-known resolvable |
|
|
|
You can also use `@Autowired` for interfaces that are well-known resolvable |
|
|
|
dependencies: `BeanFactory`, `ApplicationContext`, `Environment`, `ResourceLoader`, |
|
|
|
dependencies: `BeanFactory`, `ApplicationContext`, `Environment`, `ResourceLoader`, |
|
|
|
`ApplicationEventPublisher`, and `MessageSource`. These interfaces and their extended |
|
|
|
`ApplicationEventPublisher`, and `MessageSource`. These interfaces and their extended |
|
|
|
|