Hi guys,
I am using a session listener class to retrieve a session attribute and then serialize it as shown below:
I was expecting that when I exited my browser, the session would close and my sessionDestroyed routine would activate, creating a customer.ser file. It did not! It seems the container decides when it will terminate a session and this is not instantaneous. Anyway, I started opening more sessions and finally some began to close (session destroyed appeared on my
tomcat terminal) but I certainly did not get a serialisation file. Does anyone know why? I suspect it is something to do with deploying an application in Tomcat where you cannot access the file system as you can in a plain
Java application. Can anyone confirm this?
regards
Simon