java.lang.IllegalArgumentException: Filter mapping specifies an unknown filter name rememberCookieFilter

[andrew.bourgeois]

My web.xml looks like this:

<?xml version="1.0" encoding="UTF-8"?>

<web-app version="3.0" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd">

    <!-- Make sure that the rememberCookieFilter is executed before the mustBeSignedInFilter -->

    <filter-mapping>

        <filter-name>rememberCookieFilter</filter-name>

        <url-pattern>/*</url-pattern>

    </filter-mapping>

    <filter-mapping>

        <filter-name>mustBeSignedInFilter</filter-name>

        <url-pattern>/user/*</url-pattern>

    </filter-mapping>

</web-app>

and my filters are correctly annotated:

@WebFilter(filterName="rememberCookieFilter")

public class RememberCookieFilter implements Filter

@WebFilter(filterName="mustBeSignedInFilter")

public class MustBeSignedInFilter implements Filter

I get this error when I try to deploy:

21:10:50,160 ERROR [org.apache.catalina.core.StandardContext] (MSC service thread 1-4) Context [/webapp] startup failed due to previous errors: java.lang.IllegalArgumentException: Filter mapping specifies an unknown filter name rememberCookieFilter

          at org.apache.catalina.core.StandardContext.validateFilterMap(StandardContext.java:2040) [jbossweb-7.0.13.Final.jar:]

          at org.apache.catalina.core.StandardContext.addFilterMap(StandardContext.java:1996) [jbossweb-7.0.13.Final.jar:]

          at org.jboss.as.web.deployment.JBossContextConfig.processWebMetaData(JBossContextConfig.java:314) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final]

          at org.jboss.as.web.deployment.JBossContextConfig.applicationWebConfig(JBossContextConfig.java:169) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final]

          at org.apache.catalina.startup.ContextConfig.start(ContextConfig.java:417) [jbossweb-7.0.13.Final.jar:]

          at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:182) [jbossweb-7.0.13.Final.jar:]

          at org.jboss.as.web.deployment.JBossContextConfig.lifecycleEvent(JBossContextConfig.java:162) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final]

          at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:115) [jbossweb-7.0.13.Final.jar:]

          at org.apache.catalina.core.StandardContext.start(StandardContext.java:3790) [jbossweb-7.0.13.Final.jar:]

          at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:90) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final]

          at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811)

          at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746)

          at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0]

          at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0]

          at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0]

Tomcat had a very similar issue a few months ago:

http://stackoverflow.com/questions/10856866/using-tomcat-webfilter-doesnt-work-with-filter-mapping-inside-web-xml

My webapp works on the latest Tomcat (they fixed the issue), and it works on OpenShift (using the JBoss AS 7.1 cartdridge), but not on my local JBoss AS 7.1 installation....

[andrew.bourgeois]

The fix was to use "metadata-complete="false".

Can somebody explain why I don't need this while using Tomcat 7 or OpenShift (which uses the "latest" Jboss AS) ??

[sfcoy]

Andrew Bourgeois wrote:

The fix was to use "metadata-complete="false".

This is supposed to be the default value. Did you have to explicitly set this?

[andrew.bourgeois]

That's correct.

The JBoss developers might be able to explain so I opened a bug report for that:

https://issues.jboss.org/browse/AS7-5756

[sfcoy]

I think there's something wrong with your local environment because the attached test application works fine for me.

[andrew.bourgeois]

That example didn't work either inside Eclipse, but it did using the jboss-as plugin.

In the end Eclipse wasn't deploying the webapp correctly... and it was doing the same for my app.

Question: Is there a Maven plugin that does the same as the Tomcat 7 plugin? With that plugin I was able to launch my app as "mvn clean package tomcat7:run" and have MAVEN do the building.

It never failed me, but there doesn't seem to be such a plugin availble for JBoss. I really do hate to rely on Eclipse for the actual building. I know that you can remote debug (and use the jboss plugin to deploy to an externally running AS), but for me that's a workaround .

Thank you for your help.

[ctomc]

What about jboss-as-maven-plugin?

since version 7.2.Final has support to do jboss-as:run

https://docs.jboss.org/jbossas/7/plugins/maven/latest/usage.html

--

tomaz

[sfcoy]

Using

• Eclipse IDE for Java EE Developers
• Maven Integration (m2e) 
• Maven Integration for WTP
• JBoss Tools

works well for me. I deployed from eclipse using this setup and everything worked perfectly.

I know that a couple of years or so ago the maven integration did not work very well, but it's pretty good these days.

[andrew.bourgeois]

The jboss-as:run goals that they recently added works like a charm, thank you!