Thanks for the information guys. I'm definitely not restarting the server between deployments or using the 'keepSession' property. I'm using the built-in 'directory deployment' functionality of NetBeans which updates only the files that have changed and then invokes the browser passing a specified url to run the application. This seems to be a very fast way to develop and test so I'm not complaining from that standpoint, its just that it would be nice to not see the Exceptions rolling past on the monitor every time I redeploy. I've tested both closing the browser and leaving the browser open between re-deployments and I get the session persistence Exceptions either way. Here's one example:
PWC2785: Cannot serialize session attribute majorClassSelection for session 826e5da17c66f0d14eff63ae7b16
java.io.NotSerializableException: org.json.JSONObject
where I've placed an object into a session attribute named 'majorClassSelection'. I get this Exception (and several more) every time I redeploy.
[Message sent by forum member 'sl5337' (sl5337)]
http://forums.java.net/jive/thread.jspa?messageID=302681