It is just a bug. Thanks a lot !On 6/23/06, Eelco Hillenius [EMAIL PROTECTED] wrote:
Fixed now.EelcoOn 6/22/06, Juergen Donnerstag
[EMAIL PROTECTED] wrote: I guess it is a bug. Juergen On 6/22/06, Eelco Hillenius [EMAIL PROTECTED] wrote:
ITestPageSource is not serializable. If it was, you
Juergen Donnerstag wrote:
HTTP sessions and hence Wicket Pages get serialized and hence all it
components and variable must be serializable or transient. We enforced
that policy a little bit to make sure the error are detected earlier
and late when the application is deployed already. Just
I guess it is a bug.
Juergen
On 6/22/06, Eelco Hillenius [EMAIL PROTECTED] wrote:
ITestPageSource is not serializable. If it was, you wouldn't have this
problem. I don't use that part of Wicket myself, nor wrote it, so I'm
not sure if that interface not being serializable is intentional.
Fixed now.
Eelco
On 6/22/06, Juergen Donnerstag [EMAIL PROTECTED] wrote:
I guess it is a bug.
Juergen
On 6/22/06, Eelco Hillenius [EMAIL PROTECTED] wrote:
ITestPageSource is not serializable. If it was, you wouldn't have this
problem. I don't use that part of Wicket myself, nor wrote
Hi list,
After upgrading to Wicket 1.2, wicket tests for my project don't work
anymore. Testing a page that is initialized using a custom constructor
causes a WicketRuntimeException:
wicket.WicketRuntimeException: Internal error cloning object. Make sure
all dependent objects implement
