You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by Daniel Wu <da...@gmail.com> on 2008/03/29 22:22:19 UTC
java.io.StreamCorruptedException: invalid type code: 29
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: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: java.io.StreamCorruptedException: invalid type code: 29
Posted by Matej Knopp <ma...@gmail.com>.
passing 0 instead of -1 is definitely not the solution. This can
result in wrong page version set to other page references. I wish you
could provide a quickstart that reproduces the problem. It looks like
a bug in wicket but so far I'm not able to reproduce this behavior.
-Matej
On Fri, Apr 4, 2008 at 9:01 PM, Daniel Wu <da...@gmail.com> wrote:
> I think I've found the solution for my StreamCorruptedException problem.
> Inside the org.apache.wicket.Page, there is a constant LATEST_VERSION which
> value is -1. In my application, the versionNumber passed as parameter to
> the method getVersion(final int versionNumber) inside Page is never -1, the
> initial versionNumber of a page is always 0. When this versionNumber is
> different from 0, the versionManager object inside Page is not null, so the
> flow goes to the else block inside the getVersion() method.
>
> If LATEST_VERSION is -1, the flow of my application is always going to the
> if block below, never to else block, as my versionNumber is always >= 0, so
> depending on the versionNumber, no page will be recovered, which was leading
> to the StreamCorruptedException, maybe because wicket was trying to
> de-serialize the wrong version of my page.
>
> if (versionNumber != LATEST_VERSION) {
> page = versionManager.getVersion(versionNumber);
> }
> else {
> page = versionManager.getVersion(getCurrentVersionNumber());
> }
>
> I've changed LATEST_VERSION value to 0, and now my application works
> perfectly. Are these assumptions correct? Does anytime versionNumber assumes
> the -1 value?
>
>
>
> On Thu, Apr 3, 2008 at 8:43 PM, Daniel Wu <da...@gmail.com> wrote:
>
> > I debugged my application and it really doesn't have a
> > ClassNotFoundException eaten by ObjectInputStream. I compared the flow of
> > two screens of my application, one that works and another that doesn't:
> >
> > 1) The line 298 of SecondLevelCacheSessionStore =>
> > getLastPage().getVersion(versionNumber) is returning the correct page,
> > because inside the getVersion() method, the versionManager object is null.
> > In this case, the screen that I'm testing works perfectly.
> >
> > 2) For the screen that throws the StackOverFlow and
> > StreamCorruptedException, for some reason the versionManager object is not
> > null, and it returns a null page object.
> >
> > Another strange thing is that after the line 393 of Objects.java => return
> > ois.readObject(); => while debugging it using Eclipse, after this method
> > call the flow goes straight to the line 363 of AbstractPageStore.java,
> > without entering the finally block. So, an infinite loop starts, causing the
> > StackOverflow.
> >
> > During the tab switch of the screen that works, the line 393 of
> > Objects.java is never reached, meaning that this screen was not serialized,
> > right? This code is only reached during a tab switch of the screen that
> > throws StackOverFlow exception.
> >
> > What defines if a page should be serialized/deserialized? Does anyone know
> > what could be causing these problems?
> >
> >
> > On Wed, Apr 2, 2008 at 7:28 PM, Daniel Stoch <da...@gmail.com>
> > wrote:
> >
> > > Hi,
> > >
> > > It seems that this could be an OSGi related issue. We have the similar
> > > problem in our applications.
> > > You can look at the thread: Wicket + OSGI + Session (november 2007).
> > > Then Sebastiaan gave me a tip that this can be ClassNotFoundException:
> > >
> > > "It's probably a ClassNotFoundException on deserialization which gets
> > > eaten by ObjectInputStream (there's a bug report at Sun for this). To be
> > > sure you can debug trapping on ClassNotFoundException (caught and uncaught)
> > > when this problem occurs.
> > >
> > > However, since it's in a page you can easily fix this one: either
> > > upgrade to trunk and implement your own IClassResolver and register it with
> > > the application, or write your own IObjectStreamFactory implementation and
> > > register it with the Objects class.
> > >
> > > In either case, have a look at the DefaultObjectStreamFactory to see how
> > > to write a hook to look up classes in an ObjectInputStream implementation
> > > (resolveClass method)."
> > >
> > >
> > > Inside OSGI environment each bundle has its own class loader, so this
> > > could leeds to problem when you try to use in your app a class defined in
> > > another bundle.
> > > I've solved this problem by implementing my own IClassResolver. The
> > > default Wicket DefaultClassResolver is a final class, so we must make a copy
> > > of it and make a little change at the end of resolveClass method.
> > >
> > > The default implementation (DefaultClassResolver):
> > >
> > > synchronized (classes)
> > > {
> > > ClassLoader loader =
> > > Thread.currentThread().getContextClassLoader();
> > > if (loader == null)
> > > {
> > > loader =
> > > DefaultClassResolver.class.getClassLoader();
> > > }
> > > clazz = loader.loadClass(classname);
> > > }
> > >
> > > When there is a ClassLoader attached to the current thread as context
> > > class loader, then Wicket uses it. The problem is under OSGi, that the
> > > related class (with classname) can be located inside another bundle and can
> > > be loaded by another class loader, not this from current thread. So
> > > DefaultClassResolver fails to find this class. The solution is to try in
> > > such situation use the class loader which loads DefaultClassResolver class
> > > (= which loads all Wicket classes). In our CustomClassResolver this block
> > > was changed to something like this:
> > >
> > > synchronized (classes) {
> > > ClassLoader loader =
> > > Thread.currentThread().getContextClassLoader();
> > > if (loader == null) {
> > > loader =
> > > DefaultClassResolver.class.getClassLoader();
> > > clazz = loader.loadClass(classname);
> > > } else {
> > > try {
> > > clazz = loader.loadClass(classname);
> > > } catch (ClassNotFoundException e) {
> > > loader =
> > > DefaultClassResolver.class.getClassLoader();
> > > clazz = loader.loadClass(classname);
> > > }
> > > }
> > > }
> > >
> > > Then in your Application class init() method add the following line:
> > > getApplicationSettings().setClassResolver(new CustomClassResolver());
> > >
> > > But there is a one assumption, that bundle with Wicket classes (you
> > > probably have a Wicket bundled somehow in your app, don't you? :)), should
> > > have a dynamic import for all classes which can be located in many different
> > > bundles:
> > > DynamicImport-Package: *
> > >
> > > Maybe such change could be done in Wicket core (in DefaultClassResolver
> > > class)?
> > >
> > > --
> > > Daniel Stoch
> > >
> > >
> > > On 2008-03-29, at 22:22, Daniel Wu 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: users-unsubscribe@wicket.apache.org
> > > > For additional commands, e-mail: users-help@wicket.apache.org
> > > >
> > > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > > For additional commands, e-mail: users-help@wicket.apache.org
> > >
> > >
> >
>
--
Resizable and reorderable grid components.
http://www.inmethod.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: java.io.StreamCorruptedException: invalid type code: 29
Posted by Daniel Wu <da...@gmail.com>.
I think I've found the solution for my StreamCorruptedException problem.
Inside the org.apache.wicket.Page, there is a constant LATEST_VERSION which
value is -1. In my application, the versionNumber passed as parameter to
the method getVersion(final int versionNumber) inside Page is never -1, the
initial versionNumber of a page is always 0. When this versionNumber is
different from 0, the versionManager object inside Page is not null, so the
flow goes to the else block inside the getVersion() method.
If LATEST_VERSION is -1, the flow of my application is always going to the
if block below, never to else block, as my versionNumber is always >= 0, so
depending on the versionNumber, no page will be recovered, which was leading
to the StreamCorruptedException, maybe because wicket was trying to
de-serialize the wrong version of my page.
if (versionNumber != LATEST_VERSION) {
page = versionManager.getVersion(versionNumber);
}
else {
page = versionManager.getVersion(getCurrentVersionNumber());
}
I've changed LATEST_VERSION value to 0, and now my application works
perfectly. Are these assumptions correct? Does anytime versionNumber assumes
the -1 value?
On Thu, Apr 3, 2008 at 8:43 PM, Daniel Wu <da...@gmail.com> wrote:
> I debugged my application and it really doesn't have a
> ClassNotFoundException eaten by ObjectInputStream. I compared the flow of
> two screens of my application, one that works and another that doesn't:
>
> 1) The line 298 of SecondLevelCacheSessionStore =>
> getLastPage().getVersion(versionNumber) is returning the correct page,
> because inside the getVersion() method, the versionManager object is null.
> In this case, the screen that I'm testing works perfectly.
>
> 2) For the screen that throws the StackOverFlow and
> StreamCorruptedException, for some reason the versionManager object is not
> null, and it returns a null page object.
>
> Another strange thing is that after the line 393 of Objects.java => return
> ois.readObject(); => while debugging it using Eclipse, after this method
> call the flow goes straight to the line 363 of AbstractPageStore.java,
> without entering the finally block. So, an infinite loop starts, causing the
> StackOverflow.
>
> During the tab switch of the screen that works, the line 393 of
> Objects.java is never reached, meaning that this screen was not serialized,
> right? This code is only reached during a tab switch of the screen that
> throws StackOverFlow exception.
>
> What defines if a page should be serialized/deserialized? Does anyone know
> what could be causing these problems?
>
>
> On Wed, Apr 2, 2008 at 7:28 PM, Daniel Stoch <da...@gmail.com>
> wrote:
>
> > Hi,
> >
> > It seems that this could be an OSGi related issue. We have the similar
> > problem in our applications.
> > You can look at the thread: Wicket + OSGI + Session (november 2007).
> > Then Sebastiaan gave me a tip that this can be ClassNotFoundException:
> >
> > "It's probably a ClassNotFoundException on deserialization which gets
> > eaten by ObjectInputStream (there's a bug report at Sun for this). To be
> > sure you can debug trapping on ClassNotFoundException (caught and uncaught)
> > when this problem occurs.
> >
> > However, since it's in a page you can easily fix this one: either
> > upgrade to trunk and implement your own IClassResolver and register it with
> > the application, or write your own IObjectStreamFactory implementation and
> > register it with the Objects class.
> >
> > In either case, have a look at the DefaultObjectStreamFactory to see how
> > to write a hook to look up classes in an ObjectInputStream implementation
> > (resolveClass method)."
> >
> >
> > Inside OSGI environment each bundle has its own class loader, so this
> > could leeds to problem when you try to use in your app a class defined in
> > another bundle.
> > I've solved this problem by implementing my own IClassResolver. The
> > default Wicket DefaultClassResolver is a final class, so we must make a copy
> > of it and make a little change at the end of resolveClass method.
> >
> > The default implementation (DefaultClassResolver):
> >
> > synchronized (classes)
> > {
> > ClassLoader loader =
> > Thread.currentThread().getContextClassLoader();
> > if (loader == null)
> > {
> > loader =
> > DefaultClassResolver.class.getClassLoader();
> > }
> > clazz = loader.loadClass(classname);
> > }
> >
> > When there is a ClassLoader attached to the current thread as context
> > class loader, then Wicket uses it. The problem is under OSGi, that the
> > related class (with classname) can be located inside another bundle and can
> > be loaded by another class loader, not this from current thread. So
> > DefaultClassResolver fails to find this class. The solution is to try in
> > such situation use the class loader which loads DefaultClassResolver class
> > (= which loads all Wicket classes). In our CustomClassResolver this block
> > was changed to something like this:
> >
> > synchronized (classes) {
> > ClassLoader loader =
> > Thread.currentThread().getContextClassLoader();
> > if (loader == null) {
> > loader =
> > DefaultClassResolver.class.getClassLoader();
> > clazz = loader.loadClass(classname);
> > } else {
> > try {
> > clazz = loader.loadClass(classname);
> > } catch (ClassNotFoundException e) {
> > loader =
> > DefaultClassResolver.class.getClassLoader();
> > clazz = loader.loadClass(classname);
> > }
> > }
> > }
> >
> > Then in your Application class init() method add the following line:
> > getApplicationSettings().setClassResolver(new CustomClassResolver());
> >
> > But there is a one assumption, that bundle with Wicket classes (you
> > probably have a Wicket bundled somehow in your app, don't you? :)), should
> > have a dynamic import for all classes which can be located in many different
> > bundles:
> > DynamicImport-Package: *
> >
> > Maybe such change could be done in Wicket core (in DefaultClassResolver
> > class)?
> >
> > --
> > Daniel Stoch
> >
> >
> > On 2008-03-29, at 22:22, Daniel Wu 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: users-unsubscribe@wicket.apache.org
> > > For additional commands, e-mail: users-help@wicket.apache.org
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > For additional commands, e-mail: users-help@wicket.apache.org
> >
> >
>
Re: java.io.StreamCorruptedException: invalid type code: 29
Posted by Daniel Wu <da...@gmail.com>.
I debugged my application and it really doesn't have a
ClassNotFoundException eaten by ObjectInputStream. I compared the flow of
two screens of my application, one that works and another that doesn't:
1) The line 298 of SecondLevelCacheSessionStore =>
getLastPage().getVersion(versionNumber) is returning the correct page,
because inside the getVersion() method, the versionManager object is null.
In this case, the screen that I'm testing works perfectly.
2) For the screen that throws the StackOverFlow and
StreamCorruptedException, for some reason the versionManager object is not
null, and it returns a null page object.
Another strange thing is that after the line 393 of Objects.java => return
ois.readObject(); => while debugging it using Eclipse, after this method
call the flow goes straight to the line 363 of AbstractPageStore.java,
without entering the finally block. So, an infinite loop starts, causing the
StackOverflow.
During the tab switch of the screen that works, the line 393 of Objects.java
is never reached, meaning that this screen was not serialized, right? This
code is only reached during a tab switch of the screen that throws
StackOverFlow exception.
What defines if a page should be serialized/deserialized? Does anyone know
what could be causing these problems?
On Wed, Apr 2, 2008 at 7:28 PM, Daniel Stoch <da...@gmail.com> wrote:
> Hi,
>
> It seems that this could be an OSGi related issue. We have the similar
> problem in our applications.
> You can look at the thread: Wicket + OSGI + Session (november 2007). Then
> Sebastiaan gave me a tip that this can be ClassNotFoundException:
>
> "It's probably a ClassNotFoundException on deserialization which gets
> eaten by ObjectInputStream (there's a bug report at Sun for this). To be
> sure you can debug trapping on ClassNotFoundException (caught and uncaught)
> when this problem occurs.
>
> However, since it's in a page you can easily fix this one: either upgrade
> to trunk and implement your own IClassResolver and register it with the
> application, or write your own IObjectStreamFactory implementation and
> register it with the Objects class.
>
> In either case, have a look at the DefaultObjectStreamFactory to see how
> to write a hook to look up classes in an ObjectInputStream implementation
> (resolveClass method)."
>
>
> Inside OSGI environment each bundle has its own class loader, so this
> could leeds to problem when you try to use in your app a class defined in
> another bundle.
> I've solved this problem by implementing my own IClassResolver. The
> default Wicket DefaultClassResolver is a final class, so we must make a copy
> of it and make a little change at the end of resolveClass method.
>
> The default implementation (DefaultClassResolver):
>
> synchronized (classes)
> {
> ClassLoader loader =
> Thread.currentThread().getContextClassLoader();
> if (loader == null)
> {
> loader =
> DefaultClassResolver.class.getClassLoader();
> }
> clazz = loader.loadClass(classname);
> }
>
> When there is a ClassLoader attached to the current thread as context
> class loader, then Wicket uses it. The problem is under OSGi, that the
> related class (with classname) can be located inside another bundle and can
> be loaded by another class loader, not this from current thread. So
> DefaultClassResolver fails to find this class. The solution is to try in
> such situation use the class loader which loads DefaultClassResolver class
> (= which loads all Wicket classes). In our CustomClassResolver this block
> was changed to something like this:
>
> synchronized (classes) {
> ClassLoader loader =
> Thread.currentThread().getContextClassLoader();
> if (loader == null) {
> loader =
> DefaultClassResolver.class.getClassLoader();
> clazz = loader.loadClass(classname);
> } else {
> try {
> clazz = loader.loadClass(classname);
> } catch (ClassNotFoundException e) {
> loader =
> DefaultClassResolver.class.getClassLoader();
> clazz = loader.loadClass(classname);
> }
> }
> }
>
> Then in your Application class init() method add the following line:
> getApplicationSettings().setClassResolver(new CustomClassResolver());
>
> But there is a one assumption, that bundle with Wicket classes (you
> probably have a Wicket bundled somehow in your app, don't you? :)), should
> have a dynamic import for all classes which can be located in many different
> bundles:
> DynamicImport-Package: *
>
> Maybe such change could be done in Wicket core (in DefaultClassResolver
> class)?
>
> --
> Daniel Stoch
>
>
> On 2008-03-29, at 22:22, Daniel Wu 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: users-unsubscribe@wicket.apache.org
> > For additional commands, e-mail: users-help@wicket.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
Re: java.io.StreamCorruptedException: invalid type code: 29
Posted by Daniel Stoch <da...@gmail.com>.
Hi,
It seems that this could be an OSGi related issue. We have the
similar problem in our applications.
You can look at the thread: Wicket + OSGI + Session (november 2007).
Then Sebastiaan gave me a tip that this can be ClassNotFoundException:
"It's probably a ClassNotFoundException on deserialization which gets
eaten by ObjectInputStream (there's a bug report at Sun for this). To
be sure you can debug trapping on ClassNotFoundException (caught and
uncaught) when this problem occurs.
However, since it's in a page you can easily fix this one: either
upgrade to trunk and implement your own IClassResolver and register
it with the application, or write your own IObjectStreamFactory
implementation and register it with the Objects class.
In either case, have a look at the DefaultObjectStreamFactory to see
how to write a hook to look up classes in an ObjectInputStream
implementation (resolveClass method)."
Inside OSGI environment each bundle has its own class loader, so this
could leeds to problem when you try to use in your app a class
defined in another bundle.
I've solved this problem by implementing my own IClassResolver. The
default Wicket DefaultClassResolver is a final class, so we must make
a copy of it and make a little change at the end of resolveClass method.
The default implementation (DefaultClassResolver):
synchronized (classes)
{
ClassLoader loader = Thread.currentThread().getContextClassLoader();
if (loader == null)
{
loader = DefaultClassResolver.class.getClassLoader();
}
clazz = loader.loadClass(classname);
}
When there is a ClassLoader attached to the current thread as context
class loader, then Wicket uses it. The problem is under OSGi, that
the related class (with classname) can be located inside another
bundle and can be loaded by another class loader, not this from
current thread. So DefaultClassResolver fails to find this class. The
solution is to try in such situation use the class loader which loads
DefaultClassResolver class (= which loads all Wicket classes). In our
CustomClassResolver this block was changed to something like this:
synchronized (classes) {
ClassLoader loader = Thread.currentThread().getContextClassLoader();
if (loader == null) {
loader = DefaultClassResolver.class.getClassLoader();
clazz = loader.loadClass(classname);
} else {
try {
clazz = loader.loadClass(classname);
} catch (ClassNotFoundException e) {
loader = DefaultClassResolver.class.getClassLoader();
clazz = loader.loadClass(classname);
}
}
}
Then in your Application class init() method add the following line:
getApplicationSettings().setClassResolver(new CustomClassResolver());
But there is a one assumption, that bundle with Wicket classes (you
probably have a Wicket bundled somehow in your app, don't you? :)),
should have a dynamic import for all classes which can be located in
many different bundles:
DynamicImport-Package: *
Maybe such change could be done in Wicket core (in
DefaultClassResolver class)?
--
Daniel Stoch
On 2008-03-29, at 22:22, Daniel Wu 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.deserializ
> ePage(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: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: java.io.StreamCorruptedException: invalid type code: 29
Posted by Johan Compagner <jc...@gmail.com>.
i thought so
if you are using maps then wicket cant really resolve what is the type that
easy
then if it are all strings anyway you can ignore that log warning
But if you have other types in the map you really should type your
textfields yourself.
On Tue, Apr 8, 2008 at 12:21 AM, Wolfgang Gehner <wg...@gmail.com> wrote:
> We use CompoundPropertyModel(HashMap map) where the map has wicket-ids
> for map keys and the model value as map value.
>
> How do we bring that to ComponentPropertyModel? It doesn't have an
> Object constructor.
>
> Wolfgang
>
> On Mon, Apr 7, 2008 at 3:14 PM, Matej Knopp <ma...@gmail.com> wrote:
> > No, if you use new ComponentPropertyModel it should still work.
> >
> > -Matej
> >
> > On Tue, Apr 8, 2008 at 12:11 AM, André Souza <aa...@gmail.com>
> wrote:
> > > Is this something new to 1.3? We have 3705 uses of TextField in our
> app so
> > > far, and growing. We use CompoundPropertyModel out of the box.
> > >
> > > Does that mean the TextField(String wickedId) constructor stopped
> working
> > > with CompoundPropertyModel?
> > >
> > >
> > >
> > >
> > > On 4/7/08, Matej Knopp <ma...@gmail.com> wrote:
> > > >
> > > > Is this a new error? Looks like your models are unable to provide
> > > > target type. In that case you have to specify the property type in
> > > > your textfields, either though the TextField constructor or call
> > > > TextField.setType().
> > > >
> > > > This should not be required when you use (Component)PropertyModels
> > > > only, but when you have custom models you have to call it unless
> your
> > > > models implement IObjectClassAwareModel.
> > > >
> > > > -Matej
> > > >
> > > > On Mon, Apr 7, 2008 at 11:57 PM, André Souza <
> aandredsouza@gmail.com>
> > > > wrote:
> > > > > We are still having problems with the migration to 1.3.
> > > > >
> > > > > One fix we needed was not in the 1.3.3 release so we continued
> using
> > > > >
> > > > >
> > > >
> http://wicketstuff.org/maven/repository/org/apache/wicket/wicket/1.3-SNAPSHOT/
> > > > >
> > > > > for now.
> > > > >
> > > > > We get this on the console, repeatedly:
> > > > >
> > > > >
> > > > > WARN AbstractTextComponent () - Couldn't resolve model type of
> > > >
> > > > >
> Model:classname=[org.apache.wicket.model.CompoundPropertyModel$AttachedCompoundPropertyModel]:nestedModel=[Model:classname=[org.apache.wicket.model.CompoundPropertyModel]:nestedModel=[...],
> > > > >
> > > > > please set the type yourself.
> > > > >
> > > > > After we get this message a number of variables we have in are
> set to
> > > > null.
> > > > >
> > > > > What is the common cause of this message?
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > On 4/7/08, Johan Compagner <jc...@gmail.com> wrote:
> > > > > >
> > > > > > what do you mean?
> > > > > > that fix is no in the 1.3.3 release but will be in 1.3.4
> > > > > >
> > > > > >
> > > > > > On Mon, Apr 7, 2008 at 9:42 PM, Matej Knopp <
> matej.knopp@gmail.com>
> > > > wrote:
> > > > > >
> > > > > > > Actually, it seems that I'm wrong about this...
> > > > > > >
> > > > > > > -Matej
> > > > > > >
> > > > > > > On Mon, Apr 7, 2008 at 9:26 PM, Matej Knopp <
> matej.knopp@gmail.com>
> > > > > > wrote:
> > > > > > > > Wicket 1.3.3 was released before april 06. The overflow
> fix is
> > > > not
> > > > > > > > part of the release.
> > > > > > > >
> > > > > > > > -Matej
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > On Mon, Apr 7, 2008 at 9:13 PM, Daniel Wu <
> danielyien@gmail.com>
> > > > > > wrote:
> > > > > > > > > I've updated to the released Wicket 1.3.3, but I'm
> having the
> > > > > > > stackoverflow
> > > > > > > > > there, but it wasn't happening on the snapshot of
> april 06.
> > > > Was
> > > > > > this
> > > > > > > fix
> > > > > > > > > incorporated on the official Wicket 1.3.3 release?
> > > > > > > > >
> > > > > > > > > On Sun, Apr 6, 2008 at 6:10 PM, Johan Compagner <
> > > > > > > jcompagner@gmail.com>
> > > > > > > > > wrote:
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > > Dont know if the stream corrupt has the same root
> problem
> > > > as the
> > > > > > > > > > stackoverflow
> > > > > > > > > > But that is just fixed.
> > > > > > > > > >
> > > > > > > > > > johan
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > On Sat, Mar 29, 2008 at 11:22 PM, Daniel Wu <
> > > > > > danielyien@gmail.com>
> > > > > > > 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:
> > > > users-unsubscribe@wicket.apache.org
> > > > > > > > > > > For additional commands, e-mail:
> > > > users-help@wicket.apache.org
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > --
> > > > > > > >
> > > > > > > >
> > > > > > > > Resizable and reorderable grid components.
> > > > > > > > http://www.inmethod.com
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > Resizable and reorderable grid components.
> > > > > > > http://www.inmethod.com
> > > > > > >
> > > > > > >
> > > >
> ---------------------------------------------------------------------
> > > > > > > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > > > > > > For additional commands, e-mail:
> users-help@wicket.apache.org
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Resizable and reorderable grid components.
> > > > http://www.inmethod.com
> > > >
> > > >
> ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > > > For additional commands, e-mail: users-help@wicket.apache.org
> > > >
> > > >
> > >
> >
> >
> >
> > --
> > Resizable and reorderable grid components.
> > http://www.inmethod.com
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > For additional commands, e-mail: users-help@wicket.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
Re: java.io.StreamCorruptedException: invalid type code: 29
Posted by Wolfgang Gehner <wg...@gmail.com>.
We use CompoundPropertyModel(HashMap map) where the map has wicket-ids
for map keys and the model value as map value.
How do we bring that to ComponentPropertyModel? It doesn't have an
Object constructor.
Wolfgang
On Mon, Apr 7, 2008 at 3:14 PM, Matej Knopp <ma...@gmail.com> wrote:
> No, if you use new ComponentPropertyModel it should still work.
>
> -Matej
>
> On Tue, Apr 8, 2008 at 12:11 AM, André Souza <aa...@gmail.com> wrote:
> > Is this something new to 1.3? We have 3705 uses of TextField in our app so
> > far, and growing. We use CompoundPropertyModel out of the box.
> >
> > Does that mean the TextField(String wickedId) constructor stopped working
> > with CompoundPropertyModel?
> >
> >
> >
> >
> > On 4/7/08, Matej Knopp <ma...@gmail.com> wrote:
> > >
> > > Is this a new error? Looks like your models are unable to provide
> > > target type. In that case you have to specify the property type in
> > > your textfields, either though the TextField constructor or call
> > > TextField.setType().
> > >
> > > This should not be required when you use (Component)PropertyModels
> > > only, but when you have custom models you have to call it unless your
> > > models implement IObjectClassAwareModel.
> > >
> > > -Matej
> > >
> > > On Mon, Apr 7, 2008 at 11:57 PM, André Souza <aa...@gmail.com>
> > > wrote:
> > > > We are still having problems with the migration to 1.3.
> > > >
> > > > One fix we needed was not in the 1.3.3 release so we continued using
> > > >
> > > >
> > > http://wicketstuff.org/maven/repository/org/apache/wicket/wicket/1.3-SNAPSHOT/
> > > >
> > > > for now.
> > > >
> > > > We get this on the console, repeatedly:
> > > >
> > > >
> > > > WARN AbstractTextComponent () - Couldn't resolve model type of
> > >
> > > > Model:classname=[org.apache.wicket.model.CompoundPropertyModel$AttachedCompoundPropertyModel]:nestedModel=[Model:classname=[org.apache.wicket.model.CompoundPropertyModel]:nestedModel=[...],
> > > >
> > > > please set the type yourself.
> > > >
> > > > After we get this message a number of variables we have in are set to
> > > null.
> > > >
> > > > What is the common cause of this message?
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > On 4/7/08, Johan Compagner <jc...@gmail.com> wrote:
> > > > >
> > > > > what do you mean?
> > > > > that fix is no in the 1.3.3 release but will be in 1.3.4
> > > > >
> > > > >
> > > > > On Mon, Apr 7, 2008 at 9:42 PM, Matej Knopp <ma...@gmail.com>
> > > wrote:
> > > > >
> > > > > > Actually, it seems that I'm wrong about this...
> > > > > >
> > > > > > -Matej
> > > > > >
> > > > > > On Mon, Apr 7, 2008 at 9:26 PM, Matej Knopp <ma...@gmail.com>
> > > > > wrote:
> > > > > > > Wicket 1.3.3 was released before april 06. The overflow fix is
> > > not
> > > > > > > part of the release.
> > > > > > >
> > > > > > > -Matej
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > On Mon, Apr 7, 2008 at 9:13 PM, Daniel Wu <da...@gmail.com>
> > > > > wrote:
> > > > > > > > I've updated to the released Wicket 1.3.3, but I'm having the
> > > > > > stackoverflow
> > > > > > > > there, but it wasn't happening on the snapshot of april 06.
> > > Was
> > > > > this
> > > > > > fix
> > > > > > > > incorporated on the official Wicket 1.3.3 release?
> > > > > > > >
> > > > > > > > On Sun, Apr 6, 2008 at 6:10 PM, Johan Compagner <
> > > > > > jcompagner@gmail.com>
> > > > > > > > wrote:
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > > Dont know if the stream corrupt has the same root problem
> > > as the
> > > > > > > > > stackoverflow
> > > > > > > > > But that is just fixed.
> > > > > > > > >
> > > > > > > > > johan
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > On Sat, Mar 29, 2008 at 11:22 PM, Daniel Wu <
> > > > > danielyien@gmail.com>
> > > > > > 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:
> > > users-unsubscribe@wicket.apache.org
> > > > > > > > > > For additional commands, e-mail:
> > > users-help@wicket.apache.org
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > >
> > > > > > >
> > > > > > > Resizable and reorderable grid components.
> > > > > > > http://www.inmethod.com
> > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > Resizable and reorderable grid components.
> > > > > > http://www.inmethod.com
> > > > > >
> > > > > >
> > > ---------------------------------------------------------------------
> > > > > > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > > > > > For additional commands, e-mail: users-help@wicket.apache.org
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > >
> > >
> > > --
> > > Resizable and reorderable grid components.
> > > http://www.inmethod.com
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > > For additional commands, e-mail: users-help@wicket.apache.org
> > >
> > >
> >
>
>
>
> --
> Resizable and reorderable grid components.
> http://www.inmethod.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: java.io.StreamCorruptedException: invalid type code: 29
Posted by Matej Knopp <ma...@gmail.com>.
No, if you use new ComponentPropertyModel it should still work.
-Matej
On Tue, Apr 8, 2008 at 12:11 AM, André Souza <aa...@gmail.com> wrote:
> Is this something new to 1.3? We have 3705 uses of TextField in our app so
> far, and growing. We use CompoundPropertyModel out of the box.
>
> Does that mean the TextField(String wickedId) constructor stopped working
> with CompoundPropertyModel?
>
>
>
>
> On 4/7/08, Matej Knopp <ma...@gmail.com> wrote:
> >
> > Is this a new error? Looks like your models are unable to provide
> > target type. In that case you have to specify the property type in
> > your textfields, either though the TextField constructor or call
> > TextField.setType().
> >
> > This should not be required when you use (Component)PropertyModels
> > only, but when you have custom models you have to call it unless your
> > models implement IObjectClassAwareModel.
> >
> > -Matej
> >
> > On Mon, Apr 7, 2008 at 11:57 PM, André Souza <aa...@gmail.com>
> > wrote:
> > > We are still having problems with the migration to 1.3.
> > >
> > > One fix we needed was not in the 1.3.3 release so we continued using
> > >
> > >
> > http://wicketstuff.org/maven/repository/org/apache/wicket/wicket/1.3-SNAPSHOT/
> > >
> > > for now.
> > >
> > > We get this on the console, repeatedly:
> > >
> > >
> > > WARN AbstractTextComponent () - Couldn't resolve model type of
> >
> > > Model:classname=[org.apache.wicket.model.CompoundPropertyModel$AttachedCompoundPropertyModel]:nestedModel=[Model:classname=[org.apache.wicket.model.CompoundPropertyModel]:nestedModel=[...],
> > >
> > > please set the type yourself.
> > >
> > > After we get this message a number of variables we have in are set to
> > null.
> > >
> > > What is the common cause of this message?
> > >
> > >
> > >
> > >
> > >
> > >
> > > On 4/7/08, Johan Compagner <jc...@gmail.com> wrote:
> > > >
> > > > what do you mean?
> > > > that fix is no in the 1.3.3 release but will be in 1.3.4
> > > >
> > > >
> > > > On Mon, Apr 7, 2008 at 9:42 PM, Matej Knopp <ma...@gmail.com>
> > wrote:
> > > >
> > > > > Actually, it seems that I'm wrong about this...
> > > > >
> > > > > -Matej
> > > > >
> > > > > On Mon, Apr 7, 2008 at 9:26 PM, Matej Knopp <ma...@gmail.com>
> > > > wrote:
> > > > > > Wicket 1.3.3 was released before april 06. The overflow fix is
> > not
> > > > > > part of the release.
> > > > > >
> > > > > > -Matej
> > > > > >
> > > > > >
> > > > > >
> > > > > > On Mon, Apr 7, 2008 at 9:13 PM, Daniel Wu <da...@gmail.com>
> > > > wrote:
> > > > > > > I've updated to the released Wicket 1.3.3, but I'm having the
> > > > > stackoverflow
> > > > > > > there, but it wasn't happening on the snapshot of april 06.
> > Was
> > > > this
> > > > > fix
> > > > > > > incorporated on the official Wicket 1.3.3 release?
> > > > > > >
> > > > > > > On Sun, Apr 6, 2008 at 6:10 PM, Johan Compagner <
> > > > > jcompagner@gmail.com>
> > > > > > > wrote:
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > > Dont know if the stream corrupt has the same root problem
> > as the
> > > > > > > > stackoverflow
> > > > > > > > But that is just fixed.
> > > > > > > >
> > > > > > > > johan
> > > > > > > >
> > > > > > > >
> > > > > > > > On Sat, Mar 29, 2008 at 11:22 PM, Daniel Wu <
> > > > danielyien@gmail.com>
> > > > > 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:
> > users-unsubscribe@wicket.apache.org
> > > > > > > > > For additional commands, e-mail:
> > users-help@wicket.apache.org
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > >
> > > > > >
> > > > > > Resizable and reorderable grid components.
> > > > > > http://www.inmethod.com
> > > > > >
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Resizable and reorderable grid components.
> > > > > http://www.inmethod.com
> > > > >
> > > > >
> > ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > > > > For additional commands, e-mail: users-help@wicket.apache.org
> > > > >
> > > > >
> > > >
> > >
> >
> >
> >
> > --
> > Resizable and reorderable grid components.
> > http://www.inmethod.com
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > For additional commands, e-mail: users-help@wicket.apache.org
> >
> >
>
--
Resizable and reorderable grid components.
http://www.inmethod.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: java.io.StreamCorruptedException: invalid type code: 29
Posted by Johan Compagner <jc...@gmail.com>.
person.address.city
and when you render it that person doesn't have an adress just yet.
but i think we can even resolve it then by going over the classes
On Tue, Apr 8, 2008 at 12:26 AM, Wolfgang Gehner <wg...@gmail.com> wrote:
> Everything that needs state. And yes, that could be lists of data,
> serializable objects with hashmaps. How do you define a null
> reference?
>
> On Mon, Apr 7, 2008 at 3:22 PM, Johan Compagner <jc...@gmail.com>
> wrote:
> > still what really goes into that CPM?
> > another model? with what kind of object?
> > Does some properties go over lists or maps or object graphs with null
> > references in them?
> >
> >
> >
> > On Tue, Apr 8, 2008 at 12:11 AM, André Souza <aa...@gmail.com>
> wrote:
> >
> > > Is this something new to 1.3? We have 3705 uses of TextField in our
> app so
> > > far, and growing. We use CompoundPropertyModel out of the box.
> > >
> > > Does that mean the TextField(String wickedId) constructor stopped
> working
> > > with CompoundPropertyModel?
> > >
> > >
> > > On 4/7/08, Matej Knopp <ma...@gmail.com> wrote:
> > > >
> > > > Is this a new error? Looks like your models are unable to provide
> > > > target type. In that case you have to specify the property type in
> > > > your textfields, either though the TextField constructor or call
> > > > TextField.setType().
> > > >
> > > > This should not be required when you use (Component)PropertyModels
> > > > only, but when you have custom models you have to call it unless
> your
> > > > models implement IObjectClassAwareModel.
> > > >
> > > > -Matej
> > > >
> > > > On Mon, Apr 7, 2008 at 11:57 PM, André Souza <
> aandredsouza@gmail.com>
> > > > wrote:
> > > > > We are still having problems with the migration to 1.3.
> > > > >
> > > > > One fix we needed was not in the 1.3.3 release so we continued
> using
> > > > >
> > > > >
> > > >
> > >
> http://wicketstuff.org/maven/repository/org/apache/wicket/wicket/1.3-SNAPSHOT/
> > > > >
> > > > > for now.
> > > > >
> > > > > We get this on the console, repeatedly:
> > > > >
> > > > >
> > > > > WARN AbstractTextComponent () - Couldn't resolve model type of
> > > >
> > > > >
> > >
> Model:classname=[org.apache.wicket.model.CompoundPropertyModel$AttachedCompoundPropertyModel]:nestedModel=[Model:classname=[org.apache.wicket.model.CompoundPropertyModel]:nestedModel=[...],
> > > > >
> > > > > please set the type yourself.
> > > > >
> > > > > After we get this message a number of variables we have in are
> set to
> > > > null.
> > > > >
> > > > > What is the common cause of this message?
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > On 4/7/08, Johan Compagner <jc...@gmail.com> wrote:
> > > > > >
> > > > > > what do you mean?
> > > > > > that fix is no in the 1.3.3 release but will be in 1.3.4
> > > > > >
> > > > > >
> > > > > > On Mon, Apr 7, 2008 at 9:42 PM, Matej Knopp <
> matej.knopp@gmail.com>
> > > > wrote:
> > > > > >
> > > > > > > Actually, it seems that I'm wrong about this...
> > > > > > >
> > > > > > > -Matej
> > > > > > >
> > > > > > > On Mon, Apr 7, 2008 at 9:26 PM, Matej Knopp <
> > > matej.knopp@gmail.com>
> > > > > > wrote:
> > > > > > > > Wicket 1.3.3 was released before april 06. The overflow
> fix is
> > > > not
> > > > > > > > part of the release.
> > > > > > > >
> > > > > > > > -Matej
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > On Mon, Apr 7, 2008 at 9:13 PM, Daniel Wu <
> > > danielyien@gmail.com>
> > > > > > wrote:
> > > > > > > > > I've updated to the released Wicket 1.3.3, but I'm
> having
> > > the
> > > > > > > stackoverflow
> > > > > > > > > there, but it wasn't happening on the snapshot of
> april 06.
> > > > Was
> > > > > > this
> > > > > > > fix
> > > > > > > > > incorporated on the official Wicket 1.3.3 release?
> > > > > > > > >
> > > > > > > > > On Sun, Apr 6, 2008 at 6:10 PM, Johan Compagner <
> > > > > > > jcompagner@gmail.com>
> > > > > > > > > wrote:
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > > Dont know if the stream corrupt has the same root
> problem
> > > > as the
> > > > > > > > > > stackoverflow
> > > > > > > > > > But that is just fixed.
> > > > > > > > > >
> > > > > > > > > > johan
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > On Sat, Mar 29, 2008 at 11:22 PM, Daniel Wu <
> > > > > > danielyien@gmail.com>
> > > > > > > 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:
> > > > users-unsubscribe@wicket.apache.org
> > > > > > > > > > > For additional commands, e-mail:
> > > > users-help@wicket.apache.org
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > --
> > > > > > > >
> > > > > > > >
> > > > > > > > Resizable and reorderable grid components.
> > > > > > > > http://www.inmethod.com
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > Resizable and reorderable grid components.
> > > > > > > http://www.inmethod.com
> > > > > > >
> > > > > > >
> > > >
> ---------------------------------------------------------------------
> > > > > > > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > > > > > > For additional commands, e-mail:
> users-help@wicket.apache.org
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Resizable and reorderable grid components.
> > > > http://www.inmethod.com
> > > >
> > > >
> ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > > > For additional commands, e-mail: users-help@wicket.apache.org
> > > >
> > > >
> > >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
Re: java.io.StreamCorruptedException: invalid type code: 29
Posted by Johan Compagner <jc...@gmail.com>.
if you override it and give the type then that field can give you the
warning
On Tue, Apr 8, 2008 at 12:30 AM, Wolfgang Gehner <wg...@gmail.com> wrote:
> Is that for text fields only, or other components as well? We have a
> class RTextField that extends TextField so we override the default
> constructor RTextField(String id) to do super(id, String.class)
>
> On Mon, Apr 7, 2008 at 3:26 PM, Wolfgang Gehner <wg...@gmail.com> wrote:
> > Everything that needs state. And yes, that could be lists of data,
> > serializable objects with hashmaps. How do you define a null
> > reference?
> >
> >
> >
> > On Mon, Apr 7, 2008 at 3:22 PM, Johan Compagner <jc...@gmail.com>
> wrote:
> > > still what really goes into that CPM?
> > > another model? with what kind of object?
> > > Does some properties go over lists or maps or object graphs with
> null
> > > references in them?
> > >
> > >
> > >
> > > On Tue, Apr 8, 2008 at 12:11 AM, André Souza <aa...@gmail.com>
> wrote:
> > >
> > > > Is this something new to 1.3? We have 3705 uses of TextField in
> our app so
> > > > far, and growing. We use CompoundPropertyModel out of the box.
> > > >
> > > > Does that mean the TextField(String wickedId) constructor stopped
> working
> > > > with CompoundPropertyModel?
> > > >
> > > >
> > > > On 4/7/08, Matej Knopp <ma...@gmail.com> wrote:
> > > > >
> > > > > Is this a new error? Looks like your models are unable to
> provide
> > > > > target type. In that case you have to specify the property type
> in
> > > > > your textfields, either though the TextField constructor or call
> > > > > TextField.setType().
> > > > >
> > > > > This should not be required when you use
> (Component)PropertyModels
> > > > > only, but when you have custom models you have to call it unless
> your
> > > > > models implement IObjectClassAwareModel.
> > > > >
> > > > > -Matej
> > > > >
> > > > > On Mon, Apr 7, 2008 at 11:57 PM, André Souza <
> aandredsouza@gmail.com>
> > > > > wrote:
> > > > > > We are still having problems with the migration to 1.3.
> > > > > >
> > > > > > One fix we needed was not in the 1.3.3 release so we
> continued using
> > > > > >
> > > > > >
> > > > >
> > > >
> http://wicketstuff.org/maven/repository/org/apache/wicket/wicket/1.3-SNAPSHOT/
> > > > > >
> > > > > > for now.
> > > > > >
> > > > > > We get this on the console, repeatedly:
> > > > > >
> > > > > >
> > > > > > WARN AbstractTextComponent () - Couldn't resolve model type
> of
> > > > >
> > > > > >
> > > >
> Model:classname=[org.apache.wicket.model.CompoundPropertyModel$AttachedCompoundPropertyModel]:nestedModel=[Model:classname=[org.apache.wicket.model.CompoundPropertyModel]:nestedModel=[...],
> > > > > >
> > > > > > please set the type yourself.
> > > > > >
> > > > > > After we get this message a number of variables we have in
> are set to
> > > > > null.
> > > > > >
> > > > > > What is the common cause of this message?
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > On 4/7/08, Johan Compagner <jc...@gmail.com> wrote:
> > > > > > >
> > > > > > > what do you mean?
> > > > > > > that fix is no in the 1.3.3 release but will be in 1.3.4
> > > > > > >
> > > > > > >
> > > > > > > On Mon, Apr 7, 2008 at 9:42 PM, Matej Knopp <
> matej.knopp@gmail.com>
> > > > > wrote:
> > > > > > >
> > > > > > > > Actually, it seems that I'm wrong about this...
> > > > > > > >
> > > > > > > > -Matej
> > > > > > > >
> > > > > > > > On Mon, Apr 7, 2008 at 9:26 PM, Matej Knopp <
> > > > matej.knopp@gmail.com>
> > > > > > > wrote:
> > > > > > > > > Wicket 1.3.3 was released before april 06. The overflow
> fix is
> > > > > not
> > > > > > > > > part of the release.
> > > > > > > > >
> > > > > > > > > -Matej
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > On Mon, Apr 7, 2008 at 9:13 PM, Daniel Wu <
> > > > danielyien@gmail.com>
> > > > > > > wrote:
> > > > > > > > > > I've updated to the released Wicket 1.3.3, but I'm
> having
> > > > the
> > > > > > > > stackoverflow
> > > > > > > > > > there, but it wasn't happening on the snapshot of
> april 06.
> > > > > Was
> > > > > > > this
> > > > > > > > fix
> > > > > > > > > > incorporated on the official Wicket 1.3.3 release?
> > > > > > > > > >
> > > > > > > > > > On Sun, Apr 6, 2008 at 6:10 PM, Johan Compagner <
> > > > > > > > jcompagner@gmail.com>
> > > > > > > > > > wrote:
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > > Dont know if the stream corrupt has the same root
> problem
> > > > > as the
> > > > > > > > > > > stackoverflow
> > > > > > > > > > > But that is just fixed.
> > > > > > > > > > >
> > > > > > > > > > > johan
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > On Sat, Mar 29, 2008 at 11:22 PM, Daniel Wu <
> > > > > > > danielyien@gmail.com>
> > > > > > > > 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:
> > > > > users-unsubscribe@wicket.apache.org
> > > > > > > > > > > > For additional commands, e-mail:
> > > > > users-help@wicket.apache.org
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > --
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > Resizable and reorderable grid components.
> > > > > > > > > http://www.inmethod.com
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > --
> > > > > > > > Resizable and reorderable grid components.
> > > > > > > > http://www.inmethod.com
> > > > > > > >
> > > > > > > >
> > > > >
> ---------------------------------------------------------------------
> > > > > > > > To unsubscribe, e-mail:
> users-unsubscribe@wicket.apache.org
> > > > > > > > For additional commands, e-mail:
> users-help@wicket.apache.org
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Resizable and reorderable grid components.
> > > > > http://www.inmethod.com
> > > > >
> > > > >
> ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > > > > For additional commands, e-mail: users-help@wicket.apache.org
> > > > >
> > > > >
> > > >
> > >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
Re: java.io.StreamCorruptedException: invalid type code: 29
Posted by Wolfgang Gehner <wg...@gmail.com>.
Is that for text fields only, or other components as well? We have a
class RTextField that extends TextField so we override the default
constructor RTextField(String id) to do super(id, String.class)
On Mon, Apr 7, 2008 at 3:26 PM, Wolfgang Gehner <wg...@gmail.com> wrote:
> Everything that needs state. And yes, that could be lists of data,
> serializable objects with hashmaps. How do you define a null
> reference?
>
>
>
> On Mon, Apr 7, 2008 at 3:22 PM, Johan Compagner <jc...@gmail.com> wrote:
> > still what really goes into that CPM?
> > another model? with what kind of object?
> > Does some properties go over lists or maps or object graphs with null
> > references in them?
> >
> >
> >
> > On Tue, Apr 8, 2008 at 12:11 AM, André Souza <aa...@gmail.com> wrote:
> >
> > > Is this something new to 1.3? We have 3705 uses of TextField in our app so
> > > far, and growing. We use CompoundPropertyModel out of the box.
> > >
> > > Does that mean the TextField(String wickedId) constructor stopped working
> > > with CompoundPropertyModel?
> > >
> > >
> > > On 4/7/08, Matej Knopp <ma...@gmail.com> wrote:
> > > >
> > > > Is this a new error? Looks like your models are unable to provide
> > > > target type. In that case you have to specify the property type in
> > > > your textfields, either though the TextField constructor or call
> > > > TextField.setType().
> > > >
> > > > This should not be required when you use (Component)PropertyModels
> > > > only, but when you have custom models you have to call it unless your
> > > > models implement IObjectClassAwareModel.
> > > >
> > > > -Matej
> > > >
> > > > On Mon, Apr 7, 2008 at 11:57 PM, André Souza <aa...@gmail.com>
> > > > wrote:
> > > > > We are still having problems with the migration to 1.3.
> > > > >
> > > > > One fix we needed was not in the 1.3.3 release so we continued using
> > > > >
> > > > >
> > > >
> > > http://wicketstuff.org/maven/repository/org/apache/wicket/wicket/1.3-SNAPSHOT/
> > > > >
> > > > > for now.
> > > > >
> > > > > We get this on the console, repeatedly:
> > > > >
> > > > >
> > > > > WARN AbstractTextComponent () - Couldn't resolve model type of
> > > >
> > > > >
> > > Model:classname=[org.apache.wicket.model.CompoundPropertyModel$AttachedCompoundPropertyModel]:nestedModel=[Model:classname=[org.apache.wicket.model.CompoundPropertyModel]:nestedModel=[...],
> > > > >
> > > > > please set the type yourself.
> > > > >
> > > > > After we get this message a number of variables we have in are set to
> > > > null.
> > > > >
> > > > > What is the common cause of this message?
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > On 4/7/08, Johan Compagner <jc...@gmail.com> wrote:
> > > > > >
> > > > > > what do you mean?
> > > > > > that fix is no in the 1.3.3 release but will be in 1.3.4
> > > > > >
> > > > > >
> > > > > > On Mon, Apr 7, 2008 at 9:42 PM, Matej Knopp <ma...@gmail.com>
> > > > wrote:
> > > > > >
> > > > > > > Actually, it seems that I'm wrong about this...
> > > > > > >
> > > > > > > -Matej
> > > > > > >
> > > > > > > On Mon, Apr 7, 2008 at 9:26 PM, Matej Knopp <
> > > matej.knopp@gmail.com>
> > > > > > wrote:
> > > > > > > > Wicket 1.3.3 was released before april 06. The overflow fix is
> > > > not
> > > > > > > > part of the release.
> > > > > > > >
> > > > > > > > -Matej
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > On Mon, Apr 7, 2008 at 9:13 PM, Daniel Wu <
> > > danielyien@gmail.com>
> > > > > > wrote:
> > > > > > > > > I've updated to the released Wicket 1.3.3, but I'm having
> > > the
> > > > > > > stackoverflow
> > > > > > > > > there, but it wasn't happening on the snapshot of april 06.
> > > > Was
> > > > > > this
> > > > > > > fix
> > > > > > > > > incorporated on the official Wicket 1.3.3 release?
> > > > > > > > >
> > > > > > > > > On Sun, Apr 6, 2008 at 6:10 PM, Johan Compagner <
> > > > > > > jcompagner@gmail.com>
> > > > > > > > > wrote:
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > > Dont know if the stream corrupt has the same root problem
> > > > as the
> > > > > > > > > > stackoverflow
> > > > > > > > > > But that is just fixed.
> > > > > > > > > >
> > > > > > > > > > johan
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > On Sat, Mar 29, 2008 at 11:22 PM, Daniel Wu <
> > > > > > danielyien@gmail.com>
> > > > > > > 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:
> > > > users-unsubscribe@wicket.apache.org
> > > > > > > > > > > For additional commands, e-mail:
> > > > users-help@wicket.apache.org
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > --
> > > > > > > >
> > > > > > > >
> > > > > > > > Resizable and reorderable grid components.
> > > > > > > > http://www.inmethod.com
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > Resizable and reorderable grid components.
> > > > > > > http://www.inmethod.com
> > > > > > >
> > > > > > >
> > > > ---------------------------------------------------------------------
> > > > > > > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > > > > > > For additional commands, e-mail: users-help@wicket.apache.org
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Resizable and reorderable grid components.
> > > > http://www.inmethod.com
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > > > For additional commands, e-mail: users-help@wicket.apache.org
> > > >
> > > >
> > >
> >
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: java.io.StreamCorruptedException: invalid type code: 29
Posted by Wolfgang Gehner <wg...@gmail.com>.
Everything that needs state. And yes, that could be lists of data,
serializable objects with hashmaps. How do you define a null
reference?
On Mon, Apr 7, 2008 at 3:22 PM, Johan Compagner <jc...@gmail.com> wrote:
> still what really goes into that CPM?
> another model? with what kind of object?
> Does some properties go over lists or maps or object graphs with null
> references in them?
>
>
>
> On Tue, Apr 8, 2008 at 12:11 AM, André Souza <aa...@gmail.com> wrote:
>
> > Is this something new to 1.3? We have 3705 uses of TextField in our app so
> > far, and growing. We use CompoundPropertyModel out of the box.
> >
> > Does that mean the TextField(String wickedId) constructor stopped working
> > with CompoundPropertyModel?
> >
> >
> > On 4/7/08, Matej Knopp <ma...@gmail.com> wrote:
> > >
> > > Is this a new error? Looks like your models are unable to provide
> > > target type. In that case you have to specify the property type in
> > > your textfields, either though the TextField constructor or call
> > > TextField.setType().
> > >
> > > This should not be required when you use (Component)PropertyModels
> > > only, but when you have custom models you have to call it unless your
> > > models implement IObjectClassAwareModel.
> > >
> > > -Matej
> > >
> > > On Mon, Apr 7, 2008 at 11:57 PM, André Souza <aa...@gmail.com>
> > > wrote:
> > > > We are still having problems with the migration to 1.3.
> > > >
> > > > One fix we needed was not in the 1.3.3 release so we continued using
> > > >
> > > >
> > >
> > http://wicketstuff.org/maven/repository/org/apache/wicket/wicket/1.3-SNAPSHOT/
> > > >
> > > > for now.
> > > >
> > > > We get this on the console, repeatedly:
> > > >
> > > >
> > > > WARN AbstractTextComponent () - Couldn't resolve model type of
> > >
> > > >
> > Model:classname=[org.apache.wicket.model.CompoundPropertyModel$AttachedCompoundPropertyModel]:nestedModel=[Model:classname=[org.apache.wicket.model.CompoundPropertyModel]:nestedModel=[...],
> > > >
> > > > please set the type yourself.
> > > >
> > > > After we get this message a number of variables we have in are set to
> > > null.
> > > >
> > > > What is the common cause of this message?
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > On 4/7/08, Johan Compagner <jc...@gmail.com> wrote:
> > > > >
> > > > > what do you mean?
> > > > > that fix is no in the 1.3.3 release but will be in 1.3.4
> > > > >
> > > > >
> > > > > On Mon, Apr 7, 2008 at 9:42 PM, Matej Knopp <ma...@gmail.com>
> > > wrote:
> > > > >
> > > > > > Actually, it seems that I'm wrong about this...
> > > > > >
> > > > > > -Matej
> > > > > >
> > > > > > On Mon, Apr 7, 2008 at 9:26 PM, Matej Knopp <
> > matej.knopp@gmail.com>
> > > > > wrote:
> > > > > > > Wicket 1.3.3 was released before april 06. The overflow fix is
> > > not
> > > > > > > part of the release.
> > > > > > >
> > > > > > > -Matej
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > On Mon, Apr 7, 2008 at 9:13 PM, Daniel Wu <
> > danielyien@gmail.com>
> > > > > wrote:
> > > > > > > > I've updated to the released Wicket 1.3.3, but I'm having
> > the
> > > > > > stackoverflow
> > > > > > > > there, but it wasn't happening on the snapshot of april 06.
> > > Was
> > > > > this
> > > > > > fix
> > > > > > > > incorporated on the official Wicket 1.3.3 release?
> > > > > > > >
> > > > > > > > On Sun, Apr 6, 2008 at 6:10 PM, Johan Compagner <
> > > > > > jcompagner@gmail.com>
> > > > > > > > wrote:
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > > Dont know if the stream corrupt has the same root problem
> > > as the
> > > > > > > > > stackoverflow
> > > > > > > > > But that is just fixed.
> > > > > > > > >
> > > > > > > > > johan
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > On Sat, Mar 29, 2008 at 11:22 PM, Daniel Wu <
> > > > > danielyien@gmail.com>
> > > > > > 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:
> > > users-unsubscribe@wicket.apache.org
> > > > > > > > > > For additional commands, e-mail:
> > > users-help@wicket.apache.org
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > >
> > > > > > >
> > > > > > > Resizable and reorderable grid components.
> > > > > > > http://www.inmethod.com
> > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > Resizable and reorderable grid components.
> > > > > > http://www.inmethod.com
> > > > > >
> > > > > >
> > > ---------------------------------------------------------------------
> > > > > > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > > > > > For additional commands, e-mail: users-help@wicket.apache.org
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > >
> > >
> > > --
> > > Resizable and reorderable grid components.
> > > http://www.inmethod.com
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > > For additional commands, e-mail: users-help@wicket.apache.org
> > >
> > >
> >
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: java.io.StreamCorruptedException: invalid type code: 29
Posted by Johan Compagner <jc...@gmail.com>.
still what really goes into that CPM?
another model? with what kind of object?
Does some properties go over lists or maps or object graphs with null
references in them?
On Tue, Apr 8, 2008 at 12:11 AM, André Souza <aa...@gmail.com> wrote:
> Is this something new to 1.3? We have 3705 uses of TextField in our app so
> far, and growing. We use CompoundPropertyModel out of the box.
>
> Does that mean the TextField(String wickedId) constructor stopped working
> with CompoundPropertyModel?
>
>
> On 4/7/08, Matej Knopp <ma...@gmail.com> wrote:
> >
> > Is this a new error? Looks like your models are unable to provide
> > target type. In that case you have to specify the property type in
> > your textfields, either though the TextField constructor or call
> > TextField.setType().
> >
> > This should not be required when you use (Component)PropertyModels
> > only, but when you have custom models you have to call it unless your
> > models implement IObjectClassAwareModel.
> >
> > -Matej
> >
> > On Mon, Apr 7, 2008 at 11:57 PM, André Souza <aa...@gmail.com>
> > wrote:
> > > We are still having problems with the migration to 1.3.
> > >
> > > One fix we needed was not in the 1.3.3 release so we continued using
> > >
> > >
> >
> http://wicketstuff.org/maven/repository/org/apache/wicket/wicket/1.3-SNAPSHOT/
> > >
> > > for now.
> > >
> > > We get this on the console, repeatedly:
> > >
> > >
> > > WARN AbstractTextComponent () - Couldn't resolve model type of
> >
> > >
> Model:classname=[org.apache.wicket.model.CompoundPropertyModel$AttachedCompoundPropertyModel]:nestedModel=[Model:classname=[org.apache.wicket.model.CompoundPropertyModel]:nestedModel=[...],
> > >
> > > please set the type yourself.
> > >
> > > After we get this message a number of variables we have in are set to
> > null.
> > >
> > > What is the common cause of this message?
> > >
> > >
> > >
> > >
> > >
> > >
> > > On 4/7/08, Johan Compagner <jc...@gmail.com> wrote:
> > > >
> > > > what do you mean?
> > > > that fix is no in the 1.3.3 release but will be in 1.3.4
> > > >
> > > >
> > > > On Mon, Apr 7, 2008 at 9:42 PM, Matej Knopp <ma...@gmail.com>
> > wrote:
> > > >
> > > > > Actually, it seems that I'm wrong about this...
> > > > >
> > > > > -Matej
> > > > >
> > > > > On Mon, Apr 7, 2008 at 9:26 PM, Matej Knopp <
> matej.knopp@gmail.com>
> > > > wrote:
> > > > > > Wicket 1.3.3 was released before april 06. The overflow fix is
> > not
> > > > > > part of the release.
> > > > > >
> > > > > > -Matej
> > > > > >
> > > > > >
> > > > > >
> > > > > > On Mon, Apr 7, 2008 at 9:13 PM, Daniel Wu <
> danielyien@gmail.com>
> > > > wrote:
> > > > > > > I've updated to the released Wicket 1.3.3, but I'm having
> the
> > > > > stackoverflow
> > > > > > > there, but it wasn't happening on the snapshot of april 06.
> > Was
> > > > this
> > > > > fix
> > > > > > > incorporated on the official Wicket 1.3.3 release?
> > > > > > >
> > > > > > > On Sun, Apr 6, 2008 at 6:10 PM, Johan Compagner <
> > > > > jcompagner@gmail.com>
> > > > > > > wrote:
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > > Dont know if the stream corrupt has the same root problem
> > as the
> > > > > > > > stackoverflow
> > > > > > > > But that is just fixed.
> > > > > > > >
> > > > > > > > johan
> > > > > > > >
> > > > > > > >
> > > > > > > > On Sat, Mar 29, 2008 at 11:22 PM, Daniel Wu <
> > > > danielyien@gmail.com>
> > > > > 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:
> > users-unsubscribe@wicket.apache.org
> > > > > > > > > For additional commands, e-mail:
> > users-help@wicket.apache.org
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > >
> > > > > >
> > > > > > Resizable and reorderable grid components.
> > > > > > http://www.inmethod.com
> > > > > >
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Resizable and reorderable grid components.
> > > > > http://www.inmethod.com
> > > > >
> > > > >
> > ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > > > > For additional commands, e-mail: users-help@wicket.apache.org
> > > > >
> > > > >
> > > >
> > >
> >
> >
> >
> > --
> > Resizable and reorderable grid components.
> > http://www.inmethod.com
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > For additional commands, e-mail: users-help@wicket.apache.org
> >
> >
>
Re: java.io.StreamCorruptedException: invalid type code: 29
Posted by André Souza <aa...@gmail.com>.
Is this something new to 1.3? We have 3705 uses of TextField in our app so
far, and growing. We use CompoundPropertyModel out of the box.
Does that mean the TextField(String wickedId) constructor stopped working
with CompoundPropertyModel?
On 4/7/08, Matej Knopp <ma...@gmail.com> wrote:
>
> Is this a new error? Looks like your models are unable to provide
> target type. In that case you have to specify the property type in
> your textfields, either though the TextField constructor or call
> TextField.setType().
>
> This should not be required when you use (Component)PropertyModels
> only, but when you have custom models you have to call it unless your
> models implement IObjectClassAwareModel.
>
> -Matej
>
> On Mon, Apr 7, 2008 at 11:57 PM, André Souza <aa...@gmail.com>
> wrote:
> > We are still having problems with the migration to 1.3.
> >
> > One fix we needed was not in the 1.3.3 release so we continued using
> >
> >
> http://wicketstuff.org/maven/repository/org/apache/wicket/wicket/1.3-SNAPSHOT/
> >
> > for now.
> >
> > We get this on the console, repeatedly:
> >
> >
> > WARN AbstractTextComponent () - Couldn't resolve model type of
>
> > Model:classname=[org.apache.wicket.model.CompoundPropertyModel$AttachedCompoundPropertyModel]:nestedModel=[Model:classname=[org.apache.wicket.model.CompoundPropertyModel]:nestedModel=[...],
> >
> > please set the type yourself.
> >
> > After we get this message a number of variables we have in are set to
> null.
> >
> > What is the common cause of this message?
> >
> >
> >
> >
> >
> >
> > On 4/7/08, Johan Compagner <jc...@gmail.com> wrote:
> > >
> > > what do you mean?
> > > that fix is no in the 1.3.3 release but will be in 1.3.4
> > >
> > >
> > > On Mon, Apr 7, 2008 at 9:42 PM, Matej Knopp <ma...@gmail.com>
> wrote:
> > >
> > > > Actually, it seems that I'm wrong about this...
> > > >
> > > > -Matej
> > > >
> > > > On Mon, Apr 7, 2008 at 9:26 PM, Matej Knopp <ma...@gmail.com>
> > > wrote:
> > > > > Wicket 1.3.3 was released before april 06. The overflow fix is
> not
> > > > > part of the release.
> > > > >
> > > > > -Matej
> > > > >
> > > > >
> > > > >
> > > > > On Mon, Apr 7, 2008 at 9:13 PM, Daniel Wu <da...@gmail.com>
> > > wrote:
> > > > > > I've updated to the released Wicket 1.3.3, but I'm having the
> > > > stackoverflow
> > > > > > there, but it wasn't happening on the snapshot of april 06.
> Was
> > > this
> > > > fix
> > > > > > incorporated on the official Wicket 1.3.3 release?
> > > > > >
> > > > > > On Sun, Apr 6, 2008 at 6:10 PM, Johan Compagner <
> > > > jcompagner@gmail.com>
> > > > > > wrote:
> > > > > >
> > > > > >
> > > > > >
> > > > > > > Dont know if the stream corrupt has the same root problem
> as the
> > > > > > > stackoverflow
> > > > > > > But that is just fixed.
> > > > > > >
> > > > > > > johan
> > > > > > >
> > > > > > >
> > > > > > > On Sat, Mar 29, 2008 at 11:22 PM, Daniel Wu <
> > > danielyien@gmail.com>
> > > > 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:
> users-unsubscribe@wicket.apache.org
> > > > > > > > For additional commands, e-mail:
> users-help@wicket.apache.org
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > >
> > > > >
> > > > > Resizable and reorderable grid components.
> > > > > http://www.inmethod.com
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Resizable and reorderable grid components.
> > > > http://www.inmethod.com
> > > >
> > > >
> ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > > > For additional commands, e-mail: users-help@wicket.apache.org
> > > >
> > > >
> > >
> >
>
>
>
> --
> Resizable and reorderable grid components.
> http://www.inmethod.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
Re: java.io.StreamCorruptedException: invalid type code: 29
Posted by Matej Knopp <ma...@gmail.com>.
Is this a new error? Looks like your models are unable to provide
target type. In that case you have to specify the property type in
your textfields, either though the TextField constructor or call
TextField.setType().
This should not be required when you use (Component)PropertyModels
only, but when you have custom models you have to call it unless your
models implement IObjectClassAwareModel.
-Matej
On Mon, Apr 7, 2008 at 11:57 PM, André Souza <aa...@gmail.com> wrote:
> We are still having problems with the migration to 1.3.
>
> One fix we needed was not in the 1.3.3 release so we continued using
>
> http://wicketstuff.org/maven/repository/org/apache/wicket/wicket/1.3-SNAPSHOT/
>
> for now.
>
> We get this on the console, repeatedly:
>
>
> WARN AbstractTextComponent () - Couldn't resolve model type of
> Model:classname=[org.apache.wicket.model.CompoundPropertyModel$AttachedCompoundPropertyModel]:nestedModel=[Model:classname=[org.apache.wicket.model.CompoundPropertyModel]:nestedModel=[...],
>
> please set the type yourself.
>
> After we get this message a number of variables we have in are set to null.
>
> What is the common cause of this message?
>
>
>
>
>
>
> On 4/7/08, Johan Compagner <jc...@gmail.com> wrote:
> >
> > what do you mean?
> > that fix is no in the 1.3.3 release but will be in 1.3.4
> >
> >
> > On Mon, Apr 7, 2008 at 9:42 PM, Matej Knopp <ma...@gmail.com> wrote:
> >
> > > Actually, it seems that I'm wrong about this...
> > >
> > > -Matej
> > >
> > > On Mon, Apr 7, 2008 at 9:26 PM, Matej Knopp <ma...@gmail.com>
> > wrote:
> > > > Wicket 1.3.3 was released before april 06. The overflow fix is not
> > > > part of the release.
> > > >
> > > > -Matej
> > > >
> > > >
> > > >
> > > > On Mon, Apr 7, 2008 at 9:13 PM, Daniel Wu <da...@gmail.com>
> > wrote:
> > > > > I've updated to the released Wicket 1.3.3, but I'm having the
> > > stackoverflow
> > > > > there, but it wasn't happening on the snapshot of april 06. Was
> > this
> > > fix
> > > > > incorporated on the official Wicket 1.3.3 release?
> > > > >
> > > > > On Sun, Apr 6, 2008 at 6:10 PM, Johan Compagner <
> > > jcompagner@gmail.com>
> > > > > wrote:
> > > > >
> > > > >
> > > > >
> > > > > > Dont know if the stream corrupt has the same root problem as the
> > > > > > stackoverflow
> > > > > > But that is just fixed.
> > > > > >
> > > > > > johan
> > > > > >
> > > > > >
> > > > > > On Sat, Mar 29, 2008 at 11:22 PM, Daniel Wu <
> > danielyien@gmail.com>
> > > 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: users-unsubscribe@wicket.apache.org
> > > > > > > For additional commands, e-mail: users-help@wicket.apache.org
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > >
> > > >
> > > > Resizable and reorderable grid components.
> > > > http://www.inmethod.com
> > > >
> > >
> > >
> > >
> > > --
> > > Resizable and reorderable grid components.
> > > http://www.inmethod.com
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > > For additional commands, e-mail: users-help@wicket.apache.org
> > >
> > >
> >
>
--
Resizable and reorderable grid components.
http://www.inmethod.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: java.io.StreamCorruptedException: invalid type code: 29
Posted by André Souza <aa...@gmail.com>.
We are still having problems with the migration to 1.3.
One fix we needed was not in the 1.3.3 release so we continued using
http://wicketstuff.org/maven/repository/org/apache/wicket/wicket/1.3-SNAPSHOT/
for now.
We get this on the console, repeatedly:
WARN AbstractTextComponent () - Couldn't resolve model type of
Model:classname=[org.apache.wicket.model.CompoundPropertyModel$AttachedCompoundPropertyModel]:nestedModel=[Model:classname=[org.apache.wicket.model.CompoundPropertyModel]:nestedModel=[...],
please set the type yourself.
After we get this message a number of variables we have in are set to null.
What is the common cause of this message?
On 4/7/08, Johan Compagner <jc...@gmail.com> wrote:
>
> what do you mean?
> that fix is no in the 1.3.3 release but will be in 1.3.4
>
>
> On Mon, Apr 7, 2008 at 9:42 PM, Matej Knopp <ma...@gmail.com> wrote:
>
> > Actually, it seems that I'm wrong about this...
> >
> > -Matej
> >
> > On Mon, Apr 7, 2008 at 9:26 PM, Matej Knopp <ma...@gmail.com>
> wrote:
> > > Wicket 1.3.3 was released before april 06. The overflow fix is not
> > > part of the release.
> > >
> > > -Matej
> > >
> > >
> > >
> > > On Mon, Apr 7, 2008 at 9:13 PM, Daniel Wu <da...@gmail.com>
> wrote:
> > > > I've updated to the released Wicket 1.3.3, but I'm having the
> > stackoverflow
> > > > there, but it wasn't happening on the snapshot of april 06. Was
> this
> > fix
> > > > incorporated on the official Wicket 1.3.3 release?
> > > >
> > > > On Sun, Apr 6, 2008 at 6:10 PM, Johan Compagner <
> > jcompagner@gmail.com>
> > > > wrote:
> > > >
> > > >
> > > >
> > > > > Dont know if the stream corrupt has the same root problem as the
> > > > > stackoverflow
> > > > > But that is just fixed.
> > > > >
> > > > > johan
> > > > >
> > > > >
> > > > > On Sat, Mar 29, 2008 at 11:22 PM, Daniel Wu <
> danielyien@gmail.com>
> > 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: users-unsubscribe@wicket.apache.org
> > > > > > For additional commands, e-mail: users-help@wicket.apache.org
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > >
> > >
> > > --
> > >
> > >
> > > Resizable and reorderable grid components.
> > > http://www.inmethod.com
> > >
> >
> >
> >
> > --
> > Resizable and reorderable grid components.
> > http://www.inmethod.com
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > For additional commands, e-mail: users-help@wicket.apache.org
> >
> >
>
Re: java.io.StreamCorruptedException: invalid type code: 29
Posted by Johan Compagner <jc...@gmail.com>.
what do you mean?
that fix is no in the 1.3.3 release but will be in 1.3.4
On Mon, Apr 7, 2008 at 9:42 PM, Matej Knopp <ma...@gmail.com> wrote:
> Actually, it seems that I'm wrong about this...
>
> -Matej
>
> On Mon, Apr 7, 2008 at 9:26 PM, Matej Knopp <ma...@gmail.com> wrote:
> > Wicket 1.3.3 was released before april 06. The overflow fix is not
> > part of the release.
> >
> > -Matej
> >
> >
> >
> > On Mon, Apr 7, 2008 at 9:13 PM, Daniel Wu <da...@gmail.com> wrote:
> > > I've updated to the released Wicket 1.3.3, but I'm having the
> stackoverflow
> > > there, but it wasn't happening on the snapshot of april 06. Was this
> fix
> > > incorporated on the official Wicket 1.3.3 release?
> > >
> > > On Sun, Apr 6, 2008 at 6:10 PM, Johan Compagner <
> jcompagner@gmail.com>
> > > wrote:
> > >
> > >
> > >
> > > > Dont know if the stream corrupt has the same root problem as the
> > > > stackoverflow
> > > > But that is just fixed.
> > > >
> > > > johan
> > > >
> > > >
> > > > On Sat, Mar 29, 2008 at 11:22 PM, Daniel Wu <da...@gmail.com>
> 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: users-unsubscribe@wicket.apache.org
> > > > > For additional commands, e-mail: users-help@wicket.apache.org
> > > > >
> > > > >
> > > >
> > >
> >
> >
> >
> > --
> >
> >
> > Resizable and reorderable grid components.
> > http://www.inmethod.com
> >
>
>
>
> --
> Resizable and reorderable grid components.
> http://www.inmethod.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
Re: java.io.StreamCorruptedException: invalid type code: 29
Posted by Matej Knopp <ma...@gmail.com>.
Actually, it seems that I'm wrong about this...
-Matej
On Mon, Apr 7, 2008 at 9:26 PM, Matej Knopp <ma...@gmail.com> wrote:
> Wicket 1.3.3 was released before april 06. The overflow fix is not
> part of the release.
>
> -Matej
>
>
>
> On Mon, Apr 7, 2008 at 9:13 PM, Daniel Wu <da...@gmail.com> wrote:
> > I've updated to the released Wicket 1.3.3, but I'm having the stackoverflow
> > there, but it wasn't happening on the snapshot of april 06. Was this fix
> > incorporated on the official Wicket 1.3.3 release?
> >
> > On Sun, Apr 6, 2008 at 6:10 PM, Johan Compagner <jc...@gmail.com>
> > wrote:
> >
> >
> >
> > > Dont know if the stream corrupt has the same root problem as the
> > > stackoverflow
> > > But that is just fixed.
> > >
> > > johan
> > >
> > >
> > > On Sat, Mar 29, 2008 at 11:22 PM, Daniel Wu <da...@gmail.com> 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: users-unsubscribe@wicket.apache.org
> > > > For additional commands, e-mail: users-help@wicket.apache.org
> > > >
> > > >
> > >
> >
>
>
>
> --
>
>
> Resizable and reorderable grid components.
> http://www.inmethod.com
>
--
Resizable and reorderable grid components.
http://www.inmethod.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: java.io.StreamCorruptedException: invalid type code: 29
Posted by Matej Knopp <ma...@gmail.com>.
Wicket 1.3.3 was released before april 06. The overflow fix is not
part of the release.
-Matej
On Mon, Apr 7, 2008 at 9:13 PM, Daniel Wu <da...@gmail.com> wrote:
> I've updated to the released Wicket 1.3.3, but I'm having the stackoverflow
> there, but it wasn't happening on the snapshot of april 06. Was this fix
> incorporated on the official Wicket 1.3.3 release?
>
> On Sun, Apr 6, 2008 at 6:10 PM, Johan Compagner <jc...@gmail.com>
> wrote:
>
>
>
> > Dont know if the stream corrupt has the same root problem as the
> > stackoverflow
> > But that is just fixed.
> >
> > johan
> >
> >
> > On Sat, Mar 29, 2008 at 11:22 PM, Daniel Wu <da...@gmail.com> 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: users-unsubscribe@wicket.apache.org
> > > For additional commands, e-mail: users-help@wicket.apache.org
> > >
> > >
> >
>
--
Resizable and reorderable grid components.
http://www.inmethod.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: java.io.StreamCorruptedException: invalid type code: 29
Posted by Daniel Wu <da...@gmail.com>.
I've updated to the released Wicket 1.3.3, but I'm having the stackoverflow
there, but it wasn't happening on the snapshot of april 06. Was this fix
incorporated on the official Wicket 1.3.3 release?
On Sun, Apr 6, 2008 at 6:10 PM, Johan Compagner <jc...@gmail.com>
wrote:
> Dont know if the stream corrupt has the same root problem as the
> stackoverflow
> But that is just fixed.
>
> johan
>
>
> On Sat, Mar 29, 2008 at 11:22 PM, Daniel Wu <da...@gmail.com> 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: users-unsubscribe@wicket.apache.org
> > For additional commands, e-mail: users-help@wicket.apache.org
> >
> >
>
Re: java.io.StreamCorruptedException: invalid type code: 29
Posted by Johan Compagner <jc...@gmail.com>.
Dont know if the stream corrupt has the same root problem as the
stackoverflow
But that is just fixed.
johan
On Sat, Mar 29, 2008 at 11:22 PM, Daniel Wu <da...@gmail.com> 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: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
Re: java.io.StreamCorruptedException: invalid type code: 29
Posted by James Carman <ja...@carmanconsulting.com>.
On Wed, Apr 2, 2008 at 4:03 PM, Martijn Dashorst
<ma...@gmail.com> wrote:
> SPEED!
Can it use a special session store that serializes stuff in-memory
just to make sure the serialization is checked? Would that be fast
enough?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: java.io.StreamCorruptedException: invalid type code: 29
Posted by Matej Knopp <ma...@gmail.com>.
On Wed, Apr 2, 2008 at 10:03 PM, Martijn Dashorst
<ma...@gmail.com> wrote:
> SPEED!
Awesome. I don't give a rats ass about the unit tests performance. Is
it really worth having different environment for running unit tests
than the the environment the application runs within?
-Matej
>
>
>
> On 4/2/08, Matej Knopp <ma...@gmail.com> wrote:
> > I'm affraid we won't be able to help here without a testcase. We
> > already have a tests for this they pass, so it must be something we
> > didn't cover.
> >
> > Also that reminds me, there's problem with wicket tester, the page
> > reference serialization test (don't remember the exact name now) is
> > not running properly because wicket tester has been switched to
> > httpsessionstore. WHY? Why do we use http sessionstore with tests when
> > noone really uses httpsessionstore in production?!
> >
> > -Matej
> >
> >
> > On Wed, Apr 2, 2008 at 9:38 PM, Johan Compagner <jc...@gmail.com> wrote:
> > > 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 <ja...@carmanconsulting.com>
> > > 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 <jc...@gmail.com>
> > > > 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 <da...@gmail.com> 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 <da...@gmail.com> 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: users-unsubscribe@wicket.apache.org
> > > > > > >> For additional commands, e-mail: users-help@wicket.apache.org
> > > > > > >>
> > > > > > >>
> > > > > > >
> > > > > > >
> > > > ---------------------------------------------------------------------
> > > > > > > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > > > > > > For additional commands, e-mail: users-help@wicket.apache.org
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > > > --
> > > > > > 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: users-unsubscribe@wicket.apache.org
> > > > > > For additional commands, e-mail: users-help@wicket.apache.org
> > > > > >
> > > > > >
> > > > >
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > > > For additional commands, e-mail: users-help@wicket.apache.org
> > > >
> > > >
> > >
> >
> >
> >
> >
> > --
> > Resizable and reorderable grid components.
> > http://www.inmethod.com
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > For additional commands, e-mail: users-help@wicket.apache.org
> >
> >
>
>
> --
> Buy Wicket in Action: http://manning.com/dashorst
> Apache Wicket 1.3.2 is released
> Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.2
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
--
Resizable and reorderable grid components.
http://www.inmethod.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: java.io.StreamCorruptedException: invalid type code: 29
Posted by Martijn Dashorst <ma...@gmail.com>.
SPEED!
On 4/2/08, Matej Knopp <ma...@gmail.com> wrote:
> I'm affraid we won't be able to help here without a testcase. We
> already have a tests for this they pass, so it must be something we
> didn't cover.
>
> Also that reminds me, there's problem with wicket tester, the page
> reference serialization test (don't remember the exact name now) is
> not running properly because wicket tester has been switched to
> httpsessionstore. WHY? Why do we use http sessionstore with tests when
> noone really uses httpsessionstore in production?!
>
> -Matej
>
>
> On Wed, Apr 2, 2008 at 9:38 PM, Johan Compagner <jc...@gmail.com> wrote:
> > 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 <ja...@carmanconsulting.com>
> > 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 <jc...@gmail.com>
> > > 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 <da...@gmail.com> 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 <da...@gmail.com> 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: users-unsubscribe@wicket.apache.org
> > > > > >> For additional commands, e-mail: users-help@wicket.apache.org
> > > > > >>
> > > > > >>
> > > > > >
> > > > > >
> > > ---------------------------------------------------------------------
> > > > > > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > > > > > For additional commands, e-mail: users-help@wicket.apache.org
> > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > > --
> > > > > 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: users-unsubscribe@wicket.apache.org
> > > > > For additional commands, e-mail: users-help@wicket.apache.org
> > > > >
> > > > >
> > > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > > For additional commands, e-mail: users-help@wicket.apache.org
> > >
> > >
> >
>
>
>
>
> --
> Resizable and reorderable grid components.
> http://www.inmethod.com
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
--
Buy Wicket in Action: http://manning.com/dashorst
Apache Wicket 1.3.2 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.2
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: java.io.StreamCorruptedException: invalid type code: 29
Posted by Matej Knopp <ma...@gmail.com>.
I'm affraid we won't be able to help here without a testcase. We
already have a tests for this they pass, so it must be something we
didn't cover.
Also that reminds me, there's problem with wicket tester, the page
reference serialization test (don't remember the exact name now) is
not running properly because wicket tester has been switched to
httpsessionstore. WHY? Why do we use http sessionstore with tests when
noone really uses httpsessionstore in production?!
-Matej
On Wed, Apr 2, 2008 at 9:38 PM, Johan Compagner <jc...@gmail.com> wrote:
> 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 <ja...@carmanconsulting.com>
> 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 <jc...@gmail.com>
> > 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 <da...@gmail.com> 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 <da...@gmail.com> 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: users-unsubscribe@wicket.apache.org
> > > > >> For additional commands, e-mail: users-help@wicket.apache.org
> > > > >>
> > > > >>
> > > > >
> > > > >
> > ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > > > > For additional commands, e-mail: users-help@wicket.apache.org
> > > > >
> > > > >
> > > > >
> > > >
> > > > --
> > > > 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: users-unsubscribe@wicket.apache.org
> > > > For additional commands, e-mail: users-help@wicket.apache.org
> > > >
> > > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > For additional commands, e-mail: users-help@wicket.apache.org
> >
> >
>
--
Resizable and reorderable grid components.
http://www.inmethod.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: java.io.StreamCorruptedException: invalid type code: 29
Posted by Johan Compagner <jc...@gmail.com>.
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 <ja...@carmanconsulting.com>
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 <jc...@gmail.com>
> 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 <da...@gmail.com> 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 <da...@gmail.com> 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: users-unsubscribe@wicket.apache.org
> > > >> For additional commands, e-mail: users-help@wicket.apache.org
> > > >>
> > > >>
> > > >
> > > >
> ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > > > For additional commands, e-mail: users-help@wicket.apache.org
> > > >
> > > >
> > > >
> > >
> > > --
> > > 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: users-unsubscribe@wicket.apache.org
> > > For additional commands, e-mail: users-help@wicket.apache.org
> > >
> > >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
Re: java.io.StreamCorruptedException: invalid type code: 29
Posted by James Carman <ja...@carmanconsulting.com>.
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 <jc...@gmail.com> 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 <da...@gmail.com> 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 <da...@gmail.com> 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: users-unsubscribe@wicket.apache.org
> > >> For additional commands, e-mail: users-help@wicket.apache.org
> > >>
> > >>
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > > For additional commands, e-mail: users-help@wicket.apache.org
> > >
> > >
> > >
> >
> > --
> > 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: users-unsubscribe@wicket.apache.org
> > For additional commands, e-mail: users-help@wicket.apache.org
> >
> >
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: java.io.StreamCorruptedException: invalid type code: 29
Posted by Johan Compagner <jc...@gmail.com>.
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 <da...@gmail.com> 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 <da...@gmail.com> 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: users-unsubscribe@wicket.apache.org
> >> For additional commands, e-mail: users-help@wicket.apache.org
> >>
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > For additional commands, e-mail: users-help@wicket.apache.org
> >
> >
> >
>
> --
> 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: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
Re: java.io.StreamCorruptedException: invalid type code: 29
Posted by Daniel Wu <da...@gmail.com>.
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 <da...@gmail.com> 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: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
>
--
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: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: java.io.StreamCorruptedException: invalid type code: 29
Posted by Johan Compagner <jc...@gmail.com>.
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 <da...@gmail.com> 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: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org