with using too much
internal knowledge (e.g. the tabs-container id) of the AjaxTabbedPanel.
Sure, this is more an academically problem. But I'd like to know if
there's a better approach.
Thanks in advance!
Sven
--
subshell GmbH
Sven Schliesing
Margaretenstraße 43at +49.40.431 362
I switched over to using an anonymous overridden WebApplication:
--
WebApplication webApplication = new WebApplication() {
@Override
public Session newSession(Request request, Response response) {
return new CustomSession(request);
}
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
Yes, with a normal Wicket-Application it works just perfect.
I'm using the SpringWebApplication cause of createSpringBeanProxy() and the
automatic init of the configured ApplicationContext
(http://cwiki.apache.org/WICKET/spring.html).
Manually initializing would be a huge tradeoff for working
'
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
I think I don't get it :(
I narrowed down the problem to this test case. It would be great if you
could take a look:
---
public class WebApplicationTest {
public class CustomSession extends WebSession {
public CustomSession(Request request) {
Hi,
I'm trying to set up testing for my Wicket Application but ran across this
error message:
org.apache.wicket.protocol.http.WebSession cannot be cast to
my.CustomSession
The page (LoginPage) I'm testing does:
(CustomSession) Session.get();
This is the point where the error
