I changed the sessionStore of my application (using Wicket 2.0) to be 'wicket.protocol.http.HttpSessionStore' i.s.o. 'wicket.protocol.http.SecondLevelCacheSessionStore' (because I use methods in the AccessStackPageMap that are not supported in the pageMap of SecondLevelCacheSessionStore).
When saving my first page in the HTTPSession, HttpSessionStore tries to serialize it and throws the following exception: Caused by: java.io.NotSerializableException: wicket.response.StringResponse at java.io.ObjectOutputStream.writeObject0(Unknown Source) at java.io.ObjectOutputStream.defaultWriteFields(Unknown Source) at java.io.ObjectOutputStream.writeSerialData(Unknown Source) at java.io.ObjectOutputStream.writeOrdinaryObject(Unknown Source) at java.io.ObjectOutputStream.writeObject0(Unknown Source) at java.io.ObjectOutputStream.defaultWriteFields(Unknown Source) at java.io.ObjectOutputStream.writeSerialData(Unknown Source) at java.io.ObjectOutputStream.writeOrdinaryObject(Unknown Source) at java.io.ObjectOutputStream.writeObject0(Unknown Source) at java.io.ObjectOutputStream.writeArray(Unknown Source) at java.io.ObjectOutputStream.writeObject0(Unknown Source) at java.io.ObjectOutputStream.defaultWriteFields(Unknown Source) at java.io.ObjectOutputStream.writeSerialData(Unknown Source) at java.io.ObjectOutputStream.writeOrdinaryObject(Unknown Source) at java.io.ObjectOutputStream.writeObject0(Unknown Source) at java.io.ObjectOutputStream.writeObject(Unknown Source) at wicket.protocol.http.HttpSessionStore.setAttribute(HttpSessionStore.java:60) ... 26 more Is this a bug in Wicket ? Should StringResponse implement Serializable ? -- View this message in context: http://www.nabble.com/wicket.response.StringResponse-not-serializable-%28Wicket-2.0%29-tf2382604.html#a6640372 Sent from the Wicket - Dev mailing list archive at Nabble.com.
