Sebastien Arbogast wrote:
Upon container shutdown, Spring (or maybe the container itself) tries to be a good citizen and serialize the session to disk. Now there are some components/classes in flowscript that are not serializable, hence the session serialization fails and you get this stacktrace.
And your guess is good. I think my problem comes from a ServiceLocator singleton I use to access my Spring services. It's not a class of my own, it's automatically generated by AndroMDA and it has a shutdown() method which releases resources. It should release that NotSerializable transaction manager but the problem is how can I automatically call this method after each request or at least just before my application is shut down ?
Servlet event listeners [1] are probably what you're looking for. But i'm sure there is a "spring" way of doing this as well.
Jorg
[1] http://www.onjava.com/pub/a/onjava/2001/04/12/listeners.html
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
