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

XSD Validation error(s) #7

Closed
jusabatier opened this issue Nov 4, 2020 · 5 comments · Fixed by #9
Closed

XSD Validation error(s) #7

jusabatier opened this issue Nov 4, 2020 · 5 comments · Fixed by #9
Assignees
Labels

Comments

@jusabatier
Copy link

When starting a GN with 3.8.3 branch, I get an error with XSD validation :

Failed whilst validating schema-ident file /opt/gn_datadir/config/schema_plugins/iso19139/schema-ident.xml. Exception message if any is XSD Validation error(s):
<xsderrors>

  <error>

    <typeOfError>ERROR</typeOfError>

    <errorNumber>1</errorNumber>

    <message>cvc-complex-type.2.4.a: Invalid content was found starting with element 'title'. One of '{"http://geonetwork-opensource.org/schemas/schema-ident":appMinorVersionSupported}' is expected. (Element: title with parent element: schema)</message>

    <xpath>title[1]</xpath>

  </error>

</xsderrors>
@fvanderbiest fvanderbiest assigned cmangeat and pmauduit and unassigned cmangeat Nov 4, 2020
@jusabatier
Copy link
Author

Same problem for 'dublin-core', 'iso19110' and 'csw-record' schemas.

@pmauduit
Copy link
Member

The schema should be provided by the Geonetwork webapp, not here.

In docker setups, we are pointing the schema_dir to the exploded webapp:
https://github.com/georchestra/datadir/blob/docker-master/geonetwork/geonetwork.properties#L10

I think we should harmonize the behaviour across setups (ansible), and remove the schemas from this repository.

@landryb
Copy link
Member

landryb commented Nov 20, 2020

well originally i think the schemas were looked up in the datadir to allow user to customize them, i know at some point i had some fixes in it...

@landryb
Copy link
Member

landryb commented Nov 20, 2020

to fix the actual issue as discussed on irc, backport the XML bits from geonetwork/core-geonetwork@ac4c27d ?

@fvanderbiest
Copy link
Member

I think we should harmonize the behaviour across setups (ansible), and remove the schemas from this repository.

Standard geOrchestra datadir:

What would you propose for master ? path is not predictable...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants