GH-9192: Deprecate LobHandler usage

Fixes: #9192

With modern drivers we don't need BLOB-specific handling anymore.
The regular `PreparedStatement.setBytes()` and `ResultSet.getBytes()`
are enough for our serialized messages
This commit is contained in:
Artem Bilan
2024-06-04 17:28:17 -04:00
parent 753916ca24
commit d76174edb1
10 changed files with 610 additions and 77 deletions

View File

@@ -46,11 +46,10 @@ The following example shows some other optional attributes:
[source,xml]
----
<int-jdbc:message-store id="messageStore" data-source="dataSource"
lob-handler="lobHandler" table-prefix="MY_INT_"/>
<int-jdbc:message-store id="messageStore" data-source="dataSource" table-prefix="MY_INT_"/>
----
In the preceding example, we have specified a `LobHandler` for dealing with messages as large objects (which is often necessary for Oracle) and a prefix for the table names in the queries generated by the store.
In the preceding example, we have specified a prefix for the table names in the queries generated by the store.
The table name prefix defaults to `INT_`.
[[jdbc-message-store-channels]]

View File

@@ -23,4 +23,11 @@ In general the project has been moved to the latest dependency versions.
=== Remote File Adapters Changes
The `AbstractRemoteFileStreamingMessageSource` has now a convenient `clearFetchedCache()` API to remove references from cache for not processed remote files.
The references stay in cache because polling configuration does not allow to process all the fetched in one cycle, and the target `SessionFactory` might be changed between polling cycles, e.g. via `RotatingServerAdvice`.
The references stay in cache because polling configuration does not allow to process all the fetched in one cycle, and the target `SessionFactory` might be changed between polling cycles, e.g. via `RotatingServerAdvice`.
[[x6.4-jdbc-changes]]
=== JDBC Changes
The `LobHandler` (and respective API) has been deprecated for removal in Spring Framework `6.2`.
Respective option on `JdbcMessageStore` (and similar) have been deprecated as well.
The byte array handling for serialized message is fully deferred to JDBC driver.