So what are you referring to? The ClassCast or the IllegalState exception? For the later I'd say its a sign, that your SpringWebApplication didn't get initialized, aka it didn't find its 'ApplicationContext.xml'
I'd say have a look at the wicket-examples esp.: http://svn.apache.org/repos/asf/wicket/trunk/jdk-1.5/wicket-examples/src/main/webapp/WEB-INF/web.xml mf 2008/2/18, Sven Schliesing <[EMAIL PROTECTED]>: > > > Neither the constructor of CustomSession nor the constructor of WebSession > is > called. The error occurs much earlier, as you can see in the stack trace > posted in my first post. > > I think I will drop overriding the default session and work with > setAttribute()/getAttribute() instead. Seems to save me a lot of > trouble... > -- > View this message in context: > http://www.nabble.com/org.apache.wicket.protocol.http.WebSession-cannot-be-cast-to-my.CustomSession-tp15480791p15539346.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] > >
