-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
XML schemas not found #8446
Comments
These warnings are coming from jasper. When it initializes, it tries to load various schemas, so it can parse jsps, tlds etc. It does not use our xml schema setup in XmlParser/Catalog etc etc. It finds these .xsds and .dtds by asking the classloader that loaded the The issue is that the 6.0.0 version of the 2022-08-11 13:52:48.603:WARN :oatud.DigesterFactory:main: The XML schema [XMLSchema.dtd] could not be found. This is very likely to break XML validation if XML validation is enabled. I can't reproduce your errors for the other schemas. They are present in the 6.0.0 jar, and when I run the demos from a fresh build of 12.0.x they are found. |
Can we submit our Catalogs or EntityResolver to their handling? |
@joakime no, they look for these schemas/dtds in a |
Closing, fixed in PR #8406 |
This is still happening in Jetty Demos.
|
Same for AppEngine GoogleCloudPlatform/appengine-java-standard#107 Should I move these 3 dtd/xsd under a package that is used for resolution? |
@ludoch I replied at GoogleCloudPlatform/appengine-java-standard#107 |
Jetty version(s)
12
Description
#8406 broke XML validation. Running the demos I get:
The text was updated successfully, but these errors were encountered: