How to make Spring play nice with Wicket? (ContextLoaderListener problem)?

This is a configuration of my project: contextConfigLocation /WEB-INF/applicationContext. Xml afrodite webAppRootKey afrodite. Root log4jConfigLocation /WEB-INF/log4j.

Properties openSessionInView org.springframework.orm. Support. OpenSessionInViewFilter afrodite-app org.apache.wicket.protocol.http.

WicketFilter applicationClassName info.afrodite.wicket. AfroditeApplication configuration DEPLOYMENT openSessionInView /app/* afrodite-app /app/* org.springframework.web.util. Log4jConfigListener org.springframework.web.context.

ContextLoaderListener afrodite-api org.springframework.web.servlet. DispatcherServlet 2 afrodite-api /api/* index. Html Hope this will help.

Please check contextConfigLocation. The param-value should be classpath*:applicationContext.xml. Please check the listeners configuration also in my example.

Hope I helped! This is my web. Xml configuration which nicely works: mywebapp springRequestContextFilter org.springframework.web.filter.

RequestContextFilter contextConfigLocation classpath*:applicationContext. Xml org.springframework.web.context. ContextLoaderListener org.springframework.web.context.request.

RequestContextListener wicket. Mywebapp org.apache.wicket.protocol.http. WicketFilter applicationClassName com.company.example.web.

MyApplication filterChainProxy org.springframework.web.filter. DelegatingFilterProxy filterChainProxy /* wicket.mywebapp.

Thanks. I don't think classpath:applicationContext. Xml is the problem; this has worked for me before, and I've double-checked that applicationContext.

Xml can be found on the classpath in the resulting war. – Jonik Jun 28 at 12:17 Other than that, the main difference to my config seems to be the use of RequestContextListener and RequestContextFilter. I tried adding these but the same result: whenever ContextLoaderListener is present, Wicket won't start up.

Btw: here filter-mapping for springRequestContextFilter is missing. – Jonik Jun 28 at 12:24.

Edit: Later on I realised the root problem here most likely was missing log configuration. In our case (using SLF4J with log4j), after adding proper configuration in log4j. Properties all kinds of warnings & errors logged by libraries became visible, even with Tomcat.

I tried Jetty instead of Tomcat, and started getting better error messages. Turns out there were several libraries missing — stuff needed by some of the libraries I already used. 2011-06-28 15:57:01.879:WARN::Unable to reach node goal: started java.lang.

NoClassDefFoundError: org/apache/commons/logging/LogFactory at org.springframework.web.context.ContextLoader. InitWebApplicationContext(ContextLoader. Java:184) at org.springframework.web.context.

ContextLoaderListener. ContextInitialized(ContextLoaderListener. Java:47) at org.eclipse.jetty.server.handler.ContextHandler.

StartContext(ContextHandler. Java:640) Some of the libs apparently require commons-logging, which I added. Next: java.lang.

NoClassDefFoundError: org/springframework/asm/ClassVisitor at org.springframework.context.support. AbstractRefreshableApplicationContext. CustomizeBeanFactory(AbstractRefreshableApplicationContext.

Java:218) Added spring-asm. Next: org.springframework.beans.factory. BeanDefinitionStoreException: Unexpected exception parsing XML document from class path resource applicationContext.

Xml; nested exception is java.lang. NoClassDefFoundError: org/springframework/aop/config/AopNamespaceUtils Added spring-aop. Next something a little less straight-forward: org.springframework.beans.factory.

BeanDefinitionStoreException: Unexpected exception parsing XML document from class path resource applicationContext. Xml; nested exception is java.lang. NoClassDefFoundError: org/aopalliance/intercept/MethodInterceptor Found discussion about aopalliance missing in Spring blog comments.

Apparently it has been completely removed from spring-aop, and you need to get aopalliance. Jar from sourceforge. (I think this kind of swamp is Java EE at its worst: I don't know what spring-asm or spring-aop let alone aopalliance do, but apparently I need them.

:-P) So, added aopalliance.jar. Later I still needed to add spring-expression and cglib-2.2 (which comes with After that, some problems with my Spring/bernate persistence layer configuration remain, but they are out of scope for this question. Otherwise Wicket & Spring now work nicely (e.g. For injecting service layer objects on Wicket pages).

I guess one moral of this is that in some cases Tomcat eats useful error messages and Jetty might be better for debugging. Also, using Maven would have probably helped with the dependency hell somewhat (but it's not free of problems either).

1 I think maven dependeny management is a very good thing. I always use maven projects for java development. I'm happy that your application works.

Have a nice day! – lepike Jun 28 at 15:50 Bad tomcat server, no donnut for you! :) Since you already uses slf4j, I'd recommend you to use jcl-over-slf4j instead of commons-logging.It implements the same interfaces/classes, but redirects the calls to slf4j pipeline.

That way, your 'logging architecture' (logging has become its own science nowadays) will be cleaner and you will avoid some known classloader issues of commmons-logging. – tetsuo Jun 28 at 21:41.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.