Re: 1.5 serialization "fun"

2012-01-06 Thread nino martinez wael
Great! 2012/1/6 Martin Grigorov > Soon. A week I guess. > > On Fri, Jan 6, 2012 at 3:04 PM, nino martinez wael > wrote: > > Any idea on how far 1.5.4 are in the release process? > > > > 2012/1/6 Martin Grigorov > > > >> The problem was that Wicket doesn't produce the nice formatted error > >>

Re: 1.5 serialization "fun"

2012-01-06 Thread Martin Grigorov
Soon. A week I guess. On Fri, Jan 6, 2012 at 3:04 PM, nino martinez wael wrote: > Any idea on how far 1.5.4 are in the release process? > > 2012/1/6 Martin Grigorov > >> The problem was that Wicket doesn't produce the nice formatted error >> message pointing to the component which holds a refere

Re: 1.5 serialization "fun"

2012-01-06 Thread nino martinez wael
Any idea on how far 1.5.4 are in the release process? 2012/1/6 Martin Grigorov > 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

Re: 1.5 serialization "fun"

2012-01-06 Thread Martin Grigorov
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 wrote: > We are running 1.5.3 .. So i

Re: 1.5 serialization "fun"

2012-01-06 Thread nino martinez wael
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 > 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 > wrote: > > Hi Guys > > > > we are having an is

Re: 1.5 serialization "fun"

2012-01-06 Thread Martin Grigorov
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 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"