Jakarta EE web.xml 6.0
Servlet deployment descriptor (Jakarta EE 10)
The web.xml of Java web applications on Jakarta EE 10 servers: servlets, filters, mappings, security.
About
web.xml configures a web application for Tomcat 10.1, Jetty 12, WildFly, GlassFish and other Servlet 6.0 containers. A misspelled element is often ignored at deploy time; the schema reports it.
The schema includes the shared Jakarta EE 10 schemas (jakartaee_10, web-common_6_0, jsp_3_1 and web services client), included here.
Good to know
- Class names, URL patterns and resource references are checked for form only, not whether they exist.
- Older javax.* descriptors (web-app 4.0 and before) use the http://xmlns.jcp.org namespace and are not this schema.
- The example is by xmlvalid.com.
Files
6 files · 222.3 KB-
web-app_6_0.xsd main
-
web-common_6_0.xsd
-
jakartaee_10.xsd
-
jsp_3_1.xsd
-
xml.xsd
-
jakartaee_web_services_client_2_0.xsd
The validator loads all of these with their folder structure, so includes and imports resolve as published.
Example document
web.xml · 1 KB · valid against this schema
In CI and from code
The same schema by its name, jakarta-web-app-6.0, through the API.
npx @xmlvalid/cli validate "**/*.xml" --schema jakarta-web-app-6.0
- uses: xmlvalid/validate-action@v1
with:
files: "**/*.xml"
schema: jakarta-web-app-6.0
api-key: ${{ secrets.XMLVALID_API_KEY }}
curl https://xmlvalid.com/api/v1/validations \
-H "Authorization: Bearer $XMLVALID_API_KEY" \
-F document={{ $schema->example ?? 'document.xml' }} -F schema=jakarta-web-app-6.0
Free accounts get 100 API validations a month. On Pro, a URL monitor can check a published document against this schema every hour and email you when it breaks. More CI setups