you save the provider to the session? that's kind of an anti-pattern as it gets serialized there anyway (at least in a clustered environment). you should rather boil down to the field that causes the not-serializable exception, wicket tells you exactly which field it is anyway. or provide us some code to help you. but if you inherit from sortabledataprovider or you implement IDataProvider it shouldn't be too difficult to find out which field it is ;-)
regards, Michael TH Lim wrote: > > I tried another method. Instead of passing the reference to my > IDataProvider implementation, MyDataProvider, I recode MyDataProvider to > get it from the MySession which extends Wicket Session. I don't any > difference here but it works. I still not sure what caused MyDataProvider > to fail to persist because of the List instance it contained. > > Btw, > http://google-collections.googlecode.com/svn-history/r5/trunk/src/com/google/common/collect/LinkedListMultimap.java > LinkedListMultimap uses the inner class Node which is also Serializable. > > > Michael Sparer wrote: >> >> The Serlializable-check isn't sufficient. you can mark any class >> serializable if you want. what really counts is that all fields of the >> class are serializable, you should have a look at them ... >> > > ----- Michael Sparer http://talk-on-tech.blogspot.com -- View this message in context: http://www.nabble.com/Unable-to-serialize-class-com.google.common.collect.LinkedListMultimap%241-tp19027449p19029354.html Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
