On Mon, Jan 3, 2011 at 4:50 PM, Roman Ilin <roman.i...@gmail.com> wrote: > Hi *, > > in wicket 1.4.15 > spring 3.0.5 > hibernate 3.6 > application > > if defined springs PersistenceExceptionTranslationPostProcessor bean I > get Unserializable exceptions in > different spring classes (PersistenceExceptionTranslationInterceptor, > ChainedPersistenceExceptionTranslator, ...) > After looking into spring sources I see that they are really unserializable. > > Is there some workaround to use > PersistenceExceptionTranslationPostProcessor without redefinition of > all unserializable classes? > Or simply nobody uses PersistenceExceptionTranslationPostProcessor?
No Wicket components should be directly holding a reference to anything that contains the application context, or any post processors. The error is that something is. The unserializable exception error message is very useful in seeing what is holding on to a reference that it should not. If you can't figure it out, post the whole message (including the part where Wicket draws arrows pointing to the field that isn't serializable) in this thread. -- Jeremy Thomerson http://wickettraining.com Need a CMS for Wicket? Use Brix! http://brixcms.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
