It seems like my Spring config doesn't take effect. If I use a not existent
application class name in my applicationContext.xml the Wicket application
starts without an error message (the error with missing bean appears on first
request).
Wicket starts even with:
<bean id="wicketApplication" class="notexistent" />
Spring itself seems to work:
21.02.2009 09:56:31 org.springframework.web.context.ContextLoader
initWebApplicationContext
INFO: Root WebApplicationContext: initialization started
It looks like Wicket is starting, Spring is starting but they don't now each
other. Both should be connected in web.xml:
<filter>
<filter-name>WickiApplication</filter-name>
<filter-class>org.apache.wicket.protocol.http.WicketFilter</filter-class>
<init-param>
<param-name>applicationFactoryClassName</param-name>
<param-value>org.apache.wicket.spring.SpringWebApplicationFactory</param-value>
</init-param>
</filter>
I guess something is wrong with this. But it is like the example in "Spring in
Action" (page 311).
What can I do to integrate Spring?
Thanks
Christian
--
http://www.groovy-forum.de
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
