Spring session-scoped beans (controllers) and references to services, in terms of serialization

Question

• a standard case - you have a controller (@Controller) with @Scope(\"session\").
• classes put in the session usually are expected to i

Answer 1

In this presentation (around 1:14) the speaker says that this issue is resolved in spring 3.0 by providing a proxy of non-serializable beans, which obtains an instance from the current application context (on deserialization)