In Servlets 3.0 you don’t need a web.xml for many cases, however, sometimes it’s required or just useful. Your case is just one of them – there is no special annotations to define welcome-file list or error-pages. Another thing is – would you really like to have them hardcoded? There are some valid use-cases for … Read more
Adding metadata-complete=”true” to your web.xml should sort the issue <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” metadata-complete=”true”> This tells tomcat not to scan classes for annotations: https://web.archive.org/web/20180510163848/http://www.tomcatexpert.com/blog/2011/10/12/how-use-fragments-and-annotations-configure-your-web-application
I tried to import the servlet-api.jar to eclipse but still the same also tried to build and clean the project. I don’t use tomcat on my eclipse only have it on my net-beans. How can I solve the problem. Do not put the servlet-api.jar in your project. This is only asking for trouble. You need … Read more
The annotation is called @WebListener. And you still have to implement ServletContextListener.
I will try to summarize what I learned. To understand the problem that Servlet 3.0 and Servlet 3.1 solve, let’s look at it this way: Prior to Servlet 3.0: The problem with synchronous processing of requests is that it resulted in threads (doing heavy-lifting) running for a long time before the response goes out. If … Read more
The slow startup is caused because every single class file in every single JAR file in /WEB-INF/lib is also scanned for Servlet 3.0 specific annotations. You apparently have a lot of (large) JAR files in /WEB-INF/lib. The metadata-complete=”true” indicates that the JAR files in /WEB-INF/lib doesn’t need to be scanned for Servlet 3.0 specific annotations, … Read more
I’ve found the Servlet 3.0 Asynchronous API tricky to implement correctly and helpful documentation to be sparse. After a lot of trial and error and trying many different approaches, I was able to find a robust solution that I’ve been very happy with. When I look at my code and compare it to yours, I … Read more
Provided that you’re sure that you’re using Tomcat 7 or newer, the webapp’s web.xml has to be declared conform Servlet 3.0 spec in order to get Tomcat to scan and process the annotations. Otherwise Tomcat will still run in a fallback modus matching the Servlet version in web.xml. The support for servlet API annotations was … Read more
** PLEASE READ IF YOU USE TOMCAT OR JETTY! ** The accepted answer does work, but only if the webapp is deployed to an app server like Glassfish or Wildfly, and possibly servlet containers with EE extensions like TomEE. It doesn’t work on standard servlet containers like Tomcat, which I’m sure most people looking for … Read more
@RequestParam annotated parameters get linked to specific Servlet request parameters. Parameter values are converted to the declared method argument type. This annotation indicates that a method parameter should be bound to a web request parameter. For example Angular request for Spring RequestParam(s) would look like that: $http.post(‘http://localhost:7777/scan/l/register?username=”Johny”&password=”123123″&auth=true’) .success(function (data, status, headers, config) { … }) … Read more