t a class which extends IModel?
Also, you someone from the Wicket team confirm if my explanation above is
possible at all (PageHolder retrieving a different class when
deserializing)?
Bas
MartinM wrote:
Anybody know what is this situation? Wicket 1.4-rc4
From production:
2009-05-18 16:32:
n you share what kind of class LoginPage$1 is? (it's the first anonymous
> inner class in LoginPage) Is it a class which extends IModel?
>
> Also, you someone from the Wicket team confirm if my explanation above is
> possible at all (PageHolder retrieving a different class when
> dese
ch extends IModel?
Also, you someone from the Wicket team confirm if my explanation above is
possible at all (PageHolder retrieving a different class when
deserializing)?
Bas
MartinM wrote:
>
> Anybody know what is this situation? Wicket 1.4-rc4
>
> From production:
>
> 2009
twice by different classloaders.. Check whether the
> LoginPage class exists in both WEB-INF/classes and some other jar in your
> classpath..
>
>
> Martin Makundi wrote:
>>
>> Anybody know what is this situation? Wicket 1.4-rc4
>>
>> >From production:
>
In my experience such unexpected classcastexceptions may occur if the
same class is loaded twice by different classloaders.. Check whether the
LoginPage class exists in both WEB-INF/classes and some other jar in
your classpath..
Martin Makundi wrote:
Anybody know what is this situation
Anybody know what is this situation? Wicket 1.4-rc4
>From production:
2009-05-18 16:32:44,316 19598423 [btpool0-112] ERROR RequestCycle -
cannot assign instance of com.application.MainPage to field
wicket.quickstart.LoginPage$1.this$0 of type
wicket.quickstart.LoginPage in instance