A case of invalid Servlet3.0 annotations

explain

The deployment profile for Servlet 3.0 The top-level label for Web. XML has a Metadata-complete property that specifies whether the current deployment profile is complete. If set to true, the container will only rely on the deployment profile at deployment time, ignoring all annotations (also skipping web-fragment.xml scans, i.e. disabling pluggable support, see the following for pluggable support); If you do not configure this property, or set it to False to enable annotation support (and pluggable support) annotations valid Web. XML

<?xml version= "1.0" encoding= "iso-8859-1"?> <web-app
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/ Java EE
                      http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd "
  version=" 3.0 ">
</web-app>

invalid annotations for Web. XML

<?xml version= "1.0" encoding= "iso-8859-1"?> <web-app 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 "version=" 3.0 "metadata-complete=" t Rue "> </web-app>