[Wicket-user] Why does everything need to be Serializable when I use AjaxEventBehavior?

2006-12-17 Thread Ian Clarke
I'm a wicket newbie, but have been making relatively steady progress on a new webapp. I have an ExternalLink which is part of a Panel, and I want to make it notify the server asynchronously when the user clicks on it, so I've added an AjaxEventBehavior as follows: ExternalLink titleLink

Re: [Wicket-user] Why does everything need to be Serializable when I use AjaxEventBehavior?

2006-12-17 Thread Nick Heudecker
Somewhere you're holding a reference to the thoof.model.Story object, which is (or is attempted to be) serialized along with the referencing component to the user's session. You should look into detachable models to get around this. There are other ways to do it, but understanding detachable

Re: [Wicket-user] Why does everything need to be Serializable when I use AjaxEventBehavior?

2006-12-17 Thread Ian Clarke
On 12/17/06, Nick Heudecker [EMAIL PROTECTED] wrote: Somewhere you're holding a reference to the thoof.model.Story object, which is (or is attempted to be) serialized along with the referencing component to the user's session. You should look into detachable models to get around this. There

Re: [Wicket-user] Why does everything need to be Serializable when I use AjaxEventBehavior?

2006-12-17 Thread Erik van Oosten
Hi Ian, Since you are replying to another thread your question will probably go unnoticed. In addition the threads on nabble.com get polluted. So the message is: please only reply when you have a reply. Meanwhile: the question is very valid, so you could resend it. Regards, Erik. Ian