Skip to content
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

WFS failing with a "premature end of file" in compile XML schema #216

Open
JohannaOtt opened this issue Dec 9, 2021 · 5 comments
Open
Assignees

Comments

@JohannaOtt
Copy link

Describe the bug
When validating this WFS in the Team Engine Validator, the validation is failing with many errors. One of them is "org.xml.sax.SAXParseException; Premature end of file." in this test and I could imagine that it is also causing many of the other errors.
This is why I would like to know why this WFS causes the premature end of file error because I do not see any differences in its capabilities compared to other WFS that pass.

To Reproduce
Steps to reproduce the behavior:

  1. Go to the team engine validator
  2. Validate the WFS linked above against the WFS 2.0 test class

Expected behavior
A helpful error message on why the WFS is failing the test

Screenshots
grafik

Additional context
This is the log of the test
s0009.zip

@dstenger
Copy link
Contributor

dstenger commented Dec 9, 2021

Thank you for reporting.
We will do further investigation.

@bpross-52n
Copy link
Contributor

@JohannaOtt The problem is that the schema (DescribeFeatureType) Has imports like the following:
<import namespace="http://inspire.ec.europa.eu/schemas/act-core/4.0" schemaLocation="http://inspire.ec.europa.eu/schemas/act-core/4.0/ActivityComplex_Core.xsd"/>

The Inspire schemas have been moved to HTTPS and accessing the URL using HTTP leads to a redirect. The schema validator cannot follow this redirect. This is causing the "org.xml.sax.SAXParseException; Premature end of file."

We will try to improve the text of the error message, so the root cause can be understood better. Let me know if you have any questions or comments.

@JohannaOtt
Copy link
Author

@bpross-52n Thanks for investigating and working on the error message. You are right - when the service was created, the INSPIRE schemas still used http for importing other INSPIRE schemas.

@ghobona
Copy link
Contributor

ghobona commented Jan 26, 2022

The documentation will be updated with a note about the HTTP Redirect limitation.

@dstenger
Copy link
Contributor

We found out that the error message must be improved in ets-gml32.
New issue for improving error message: opengeospatial/ets-gml32#66

@dstenger dstenger added this to CITE Aug 1, 2024
@dstenger dstenger moved this to To do in CITE Aug 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: To do
Development

No branches or pull requests

4 participants