No that warning doesnt anything todo with serialization. But do you have a reproduceable testcase? That would be very nice to have, can you attach that to the jira (there is already one describing this i think)
On 3/29/08, Daniel Wu <[EMAIL PROTECTED]> wrote: > > I've updated my wicket application to Wicket 1.3.2, but now, when I try to > switch between my application tabs (my tabs extend > org.apache.wicket.extensions.markup.html.tabs.AbstractTab) I'm getting this > error: > > ERROR RequestCycle () - Could not deserialize object using > `org.apache.wicket.util.io.IObjectStreamFactory$DefaultObjectStreamFactory` > object factory > java.lang.RuntimeException: Could not deserialize object using > `org.apache.wicket.util.io.IObjectStreamFactory$DefaultObjectStreamFactory` > object factory > at > org.apache.wicket.util.lang.Objects.byteArrayToObject(Objects.java:411) > at > org.apache.wicket.protocol.http.pagestore.AbstractPageStore.deserializePage(AbstractPageStore.java:228) > at > org.apache.wicket.protocol.http.pagestore.DiskPageStore.getPage(DiskPageStore.java:706) > at > org.apache.wicket.protocol.http.SecondLevelCacheSessionStore$SecondLevelCachePageMap.get(SecondLevelCacheSessionStore.java:311) > at org.apache.wicket.Session.getPage(Session.java:751) > ... > Caused by: java.io.StreamCorruptedException: invalid type code: 29 > at java.io.ObjectInputStream.readObject0(Unknown Source) > at java.io.ObjectInputStream.defaultReadFields(Unknown Source) > at java.io.ObjectInputStream.readSerialData(Unknown Source) > at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source) > at java.io.ObjectInputStream.readObject0(Unknown Source) > at java.io.ObjectInputStream.readObject(Unknown Source) > at > org.apache.wicket.util.lang.Objects.byteArrayToObject(Objects.java:393) > > I've already downloaded and used the latest wicket 1.3 snapshot, which was > suggested to me here: https://issues.apache.org/jira/browse/WICKET-1445 , > but I'm still having this error. > > I'm still using an old release of wicket-extensions. Since I updated to > wicket 1.3, I'm also having this warning: > > WARN AbstractTextComponent () - Couldn't resolve model type of > Model:classname=[...], please set the type yourself. > > Could any of these be related to the Serialization error? Does anyone have > any idea of what is causing it? > > Daniel > > -- > View this message in context: > http://www.nabble.com/java.io.StreamCorruptedException%3A-invalid-type-code%3A-29-tp16374745p16374745.html > Sent from the Wicket - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
