[ https://issues.apache.org/jira/browse/WICKET-3147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12928949#action_12928949 ]
Hudson commented on WICKET-3147: -------------------------------- Integrated in Apache Wicket 1.5.x #488 (See [https://hudson.apache.org/hudson/job/Apache%20Wicket%201.5.x/488/]) WICKET-3147 Servlet 3 Annotation @WebFilter is not supported Allow 'filterPath' to be "". Both org.apache.wicket.protocol.http.WicketFilter.getFilterPathFromConfig(FilterConfig) and org.apache.wicket.protocol.http.WicketFilter.getFilterPathFromWebXml(boolean, FilterConfig) could return "". WICKET-3147 Servlet 3 Annotation @WebFilter is not supported Revert the changes in pom.xml so that Wicket depends on Servlet API 2.3 again > Servlet 3 Annotation @WebFilter is not supported > ------------------------------------------------ > > Key: WICKET-3147 > URL: https://issues.apache.org/jira/browse/WICKET-3147 > Project: Wicket > Issue Type: Improvement > Components: wicket > Affects Versions: 1.4.9, 1.4.10, 1.4.13 > Environment: Glassfish 3 > Reporter: Zeti > Assignee: Martin Grigorov > Fix For: 1.6.0 > > Attachments: wicket.tgz > > > Trying to run my application this way: > @WebFilter(value="/*", urlPatterns="/*", initParams = { > @WebInitParam( > name="applicationClassName", > value="de.logviewer.HomeApp" > ) > } > ) > public class HomeFilter extends WicketFilter{ } > results in the follwing exception: > Servlet.service() for servlet default threw exception > java.lang.IllegalArgumentException: Error initializing WicketFilter - you > have no <filter-mapping> element with a url-pattern that uses filter: > de.logviewer.HomeFilter at > org.apache.wicket.protocol.http.WicketFilter.getFilterPath(WicketFilter.java:930) > at org.apache.wicket.protocol.http.WicketFilter.init(WicketFilter.java:677) > at > org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:259) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:215) > at > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:277) > at > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:188) > at > org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:641) > at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:97) at > com.sun.enterprise.web.PESessionLockingStandardPipeline.invoke(PESessionLockingStandardPipeline.java:85) > at > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:185) > at > org.apache.catalina.connector.CoyoteAdapter.doService(CoyoteAdapter.java:325) > at > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:226) > at > com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:165) > at com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:791) > at com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:693) at > com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:954) at > com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:170) > at > com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:135) > at > com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:102) > at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:88) > at com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:76) > at > com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:53) > at > com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:57) > at com.sun.grizzly.ContextTask.run(ContextTask.java:69) at > com.sun.grizzly.util.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:330) > at > com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool.java:309) > at java.lang.Thread.run(Thread.java:662) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.