The problem was that Wicket doesn't produce the nice formatted error
message pointing to the component which holds a reference to the
non-serializable class.

https://issues.apache.org/jira/browse/WICKET-4264

On Fri, Jan 6, 2012 at 2:27 PM, nino martinez wael
<nino.martinez.w...@gmail.com> wrote:
> We are running 1.5.3 .. So it's in trunk I guess, do you know what the
> error did?
>
> 2012/1/6 Martin Grigorov <mgrigo...@apache.org>
>
>> There was a bug in SerializationChecker which is fixed either in 1.5.3 or
>> trunk.
>>
>> On Fri, Jan 6, 2012 at 2:07 PM, nino martinez wael
>> <nino.martinez.w...@gmail.com> wrote:
>> > Hi Guys
>> >
>> > we are having an issue on one of our more complex pages and are getting
>> an
>> > error like this:
>> >
>> > 2012-01-06 12:29:20,057 ERROR ["http-bio-8080"-exec-10]
>> > (JavaSerializer.java:94) - Error serializing object class
>> > com.netdesign.wallboard.page.ViewerPage [object=[Page class =
>> > com.netdesign.wallboard.page.ViewerPage, id = 14, render count = 1]]
>> > java.io.NotSerializableException:
>> com.google.inject.internal.InjectorImpl$4
>> >
>> > Problem are that there are no injector in our ViewerPage like the message
>> > are saying there are, so our idea are that it is in one of the sub
>> panels.
>> > Aren't there a way to get further knowledge about the containing
>> > component/class of the failing serialization?
>> >
>> > -regards Nino
>>
>>
>>
>> --
>> Martin Grigorov
>> jWeekend
>> Training, Consulting, Development
>> http://jWeekend.com
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>> For additional commands, e-mail: users-h...@wicket.apache.org
>>
>>



-- 
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Reply via email to