Re: @SpringBean attr null after back button

2009-01-28 Thread Igor Vaynberg
make sure you dont declare those fields as transient. -igor On Wed, Jan 28, 2009 at 10:00 AM, Thies Edeling th...@rrm.net wrote: Spring injected beans using the @SpringBean annotation seem to be null when I return to a page using the back button. I now reinject them manually using the

Re: @SpringBean attr null after back button

2009-01-28 Thread Thies Edeling
it isn't, that's what surprised me as it's a normal field. Igor Vaynberg wrote: make sure you dont declare those fields as transient. -igor On Wed, Jan 28, 2009 at 10:00 AM, Thies Edeling th...@rrm.net wrote: Spring injected beans using the @SpringBean annotation seem to be null when I

Re: @SpringBean attr null after back button

2009-01-28 Thread Igor Vaynberg
do you call Objects#setObjectStreamFactory to set wicket's objectstreamfractory instead of the default? wicket's doesnt handle proxies which may result in you seeing nulls. -igor On Wed, Jan 28, 2009 at 11:44 AM, Thies Edeling th...@rrm.net wrote: it isn't, that's what surprised me as it's a

Re: @SpringBean attr null after back button

2009-01-28 Thread Thies Edeling
no I didn't, will try that but I thought that was default on 1.3 ? (running 1.3.5) Igor Vaynberg wrote: do you call Objects#setObjectStreamFactory to set wicket's objectstreamfractory instead of the default? wicket's doesnt handle proxies which may result in you seeing nulls. -igor On Wed,

Re: @SpringBean attr null after back button

2009-01-28 Thread Igor Vaynberg
no, the default is the standard one. the standard one is used by default so unless you tweaked it there shouldnt be a problem. -igor On Wed, Jan 28, 2009 at 3:59 PM, Thies Edeling tedel...@gmail.com wrote: no I didn't, will try that but I thought that was default on 1.3 ? (running 1.3.5)