You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by Mikko Pukki <Mi...@syncrontech.com> on 2011/10/27 15:39:49 UTC

WicketFilter cannot resolve filterPath if filterMappingUrlPattern is not configured

Hi,

We noticed this while running our application in an environment where firewall blocks all connections to outside addresses.
Adding filterMappingUrlPattern parameter helped.

so for instance helloworld's web.xml (http://wicket.apache.org/learn/examples/helloworld.html) would be something like:

<web-app>
    <display-name>Wicket Examples</display-name>
    <filter>
        <filter-name>HelloWorldApplication</filter-name>
        <filter-class>org.apache.wicket.protocol.http.WicketFilter</filter-class>
        <init-param>
          <param-name>applicationClassName</param-name>
          <param-value>org.apache.wicket.examples.helloworld.HelloWorldApplication</param-value>
        </init-param>
        <init-param>
          <param-name>filterMappingUrlPattern</param-name>
          <param-value>/*</param-value>
        </init-param>
    </filter>
    <filter-mapping>
        <filter-name>HelloWorldApplication</filter-name>
        <url-pattern>/*</url-pattern>
    </filter-mapping>
</web-app>


Regards,
Mikko