Hi all,
Good news. The Memory Leak issue is fixed by updgrading the wicket
version to 1.5.4. Thanks to everyone for the support
//Madhusudhan S
-
//Maddy
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Regarding-Stack-Overflow-exception-tp4203930p4511565.html
Can anyone let me know about the entry in *Apache Wicket* /change log/ which
talks about serialization error fix?
-
//Maddy
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Regarding-Stack-Overflow-exception-tp4203930p4288315.html
Sent from the Users forum mailing
I have tried with 1.5.2 and tried by migrating few classes and tested the
small feature which was part of stack overflow message error...And now, the
fix is working fine locally
I have to upgrade complete application to 1.5.2 and update you the results
sooner
Thanks for the support :)
-
Hi,
Can you please suggest the version in which serialization issue is fixed.
Even in the change log, I am not able to find the relevant entry of
serialization fix?
-
//Maddy
--
View this message in context:
Thanks for the reply
I was also bothered about this serialization issue in wicket version 1.4.17.
Still not sure, the latest version (1.5.3) of wicket will resolve the issue
because I haven't find any migration changes statement which states about
this serialization fix @
