yes very complex code but found it PageSerializer also adds it to the used pages again..
On Wed, Apr 2, 2008 at 9:36 PM, James Carman <[EMAIL PROTECTED]> wrote: > Doesn't the code remember what it has already taken care of during > serialization? I seem to remember something like that in the code. > > On Wed, Apr 2, 2008 at 3:34 PM, Johan Compagner <[EMAIL PROTECTED]> > wrote: > > that method is only called when you have page references inside your > page > > that is going to be (or was) serialized. > > It holds the page info so that it can get it from the session also. > > > > Maybe in here we have a cycle that we dont really catch > > so Page A <-> Page B are both pointing to each other. > > > > i am not quickly looking at the code but dont immediately see how we > handle > > that > > > > johan > > > > > > > > > > On Wed, Apr 2, 2008 at 9:26 PM, Daniel Wu <[EMAIL PROTECTED]> wrote: > > > > > > > > I don't have a reproduceable testcase because the architecture that > I'm > > > using > > > is a little bit different, it uses Wicket together with OSGi, running > as > > > an > > > Eclipse plugin. > > > > > > I've noticed that this > > > java.io.StreamCorruptedExceptionStreamCorruptedException happens > after a > > > java.lang.StackOverflowError. The line 363 of AbstractPageStore > class, > > > inside the readResolve() method, is being called several times, > causing > > > the > > > java.lang.StackOverflowError. This is weird, because I've another > screen > > > which never calls this readResolve() method. > > > > > > When this method should be called? > > > > > > > > > Johan Compagner wrote: > > > > > > > > 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] > > > > > > > > > > > > > > > > > > -- > > > View this message in context: > > > > http://www.nabble.com/java.io.StreamCorruptedException%3A-invalid-type-code%3A-29-tp16374745p16449230.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] > >
