Home > Beyond, typo > Configuration Errors on Spring + Wicket

Configuration Errors on Spring + Wicket

October 11, 2016 Leave a comment Go to comments

When facing error:
The matching wildcard is strict, but no declaration can be found for element ‘context:component-scan’.

Remember, is a typo somewhere!

If you face error:
No WebApplicationContext found: no ContextLoaderListener registered?

You need to set manually the applicationContext on the setUp() of your test.

public ServletContext getServletContext() {
                ServletContext sc = super.getServletContext();
                XmlWebApplicationContext appCont = new XmlWebApplicationContext();

                sc.setAttribute(WebApplicationContext.ROOT_WEB_APPLICATION_CONTEXT_ATTRIBUTE, appCont);

                return sc;

When error BeanDefinitionStoreException Failed to read candidate component class you got a pom.xml with spring dependencies in conflict.

Categories: Beyond, typo
  1. No comments yet.
  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: