Any way to force JdbcTemplate to use a specific Connection?

[wpoitras]

Oh, and the reason why I wasn't that fond of using the SingleConnectionDataSource was because I could find a way of doing it while still keeping my business objects stateless. Although with a ThreadLocal SingleConnectionDataSource it might be possible.

[trisberg]

Thinking about it a little bit more, a ThreadConnectionDataSourc might be a good complement to the SingleConnectionDataSource. The trouble is detecting when one Session ends and the next Session starts running on a specific thread. Somehow your application would have to signal these events.

[trisberg]

I guess wrapping the service method with an AOP around advice would work here.

[Juergen Hoeller]

Note that you could still leverage Spring transaction demarcation without an actual database transaction backing it: through specifying "PROPAGATION_SUPPORTS" with the default synchronization behavior.

Even in case of SUPPORTS, Spring will still activate transaction synchronization for the demarcated scope, allowing data access code to synchronize its resources accordingly. This will lead to the same JDBC Connection (and Hibernate Session etc) used throughout that scope, even without an actual database transaction.

No need for a SingleConnectionDataSource or the like in this scenario. This seems to be what you want to achieve... and you would get it without any custom coding.

Juergen

[davsclaus]

Note that you could still leverage Spring transaction demarcation without an actual database transaction backing it: through specifying "PROPAGATION_SUPPORTS" with the default synchronization behavior.

Even in case of SUPPORTS, Spring will still activate transaction synchronization for the demarcated scope, allowing data access code to synchronize its resources accordingly. This will lead to the same JDBC Connection (and Hibernate Session etc) used throughout that scope, even without an actual database transaction.

No need for a SingleConnectionDataSource or the like in this scenario. This seems to be what you want to achieve... and you would get it without any custom coding.

Juergen

Wau sounds cool. Shouldn't this be documented in the reference manual?

[wpoitras]

Note that you could still leverage Spring transaction demarcation without an actual database transaction backing it: through specifying "PROPAGATION_SUPPORTS" with the default synchronization behavior.

Wow. This is exactly what I was looking for. Thanks.