Nope. But the exception should be in logs anyway. -Matej
On Tue, Apr 1, 2008 at 9:26 PM, James Carman <[EMAIL PROTECTED]> wrote: > Oh, ok. I thought since it was merely logging the error that it was > going on in the thread. So, Wicket doesn't stop your request if the > page's data can't be serialized? > > > > On Tue, Apr 1, 2008 at 3:19 PM, Matej Knopp <[EMAIL PROTECTED]> wrote: > > But that's just saving. The serialization itself is done in the > > request thread. Only saving of the bytearray is done in separate > > thread. > > > > There's a good reason for serializing the page in the request thread. > > We cache the serialized page data so when servlet container replicates > > the session we reuse the cached data. Also there were some locking and > > concurrency issues when we serialized the page in separate thread. > > > > -Matej > > > > > > > > On Tue, Apr 1, 2008 at 9:15 PM, James Carman <[EMAIL PROTECTED]> wrote: > > > On Tue, Apr 1, 2008 at 3:13 PM, lars vonk <[EMAIL PROTECTED]> wrote: > > > > The Exception is only logged (as ERROR) if something is not > serializable, so > > > > it will only complain in your logfile. See > Objects.objectToByteArray() > > > > method. > > > > > > > > I don't think page serialization is done in a seperate Thread > though. I > > > > couldn't find this in the code. But please correct me if I am wrong. > > > > > > > > > > Check out DiskPageStore.PageSavingThread. If you pause your > > > application, you'll see that one of those is running. > > > > > > > > > > > -- > > > > > > Resizable and reorderable grid components. > > http://www.inmethod.com > > > -- Resizable and reorderable grid components. http://www.inmethod.com
