Some types of workspace resources always fail to initialize if no internet connection is available

[MrSnyder]

Observed with deegree webservices 3.3.13, vanilla Utah workspace.

Startup works fine with internet connection. Without it, some resources (e.g. themes) won't initialize with an error message that indicates a schema issue:

[12:50:28]  INFO: [AbstractResourceManager] --------------------------------------------------------------------------------
[12:50:28]  INFO: [AbstractResourceManager] Setting up themes.
[12:50:28]  INFO: [AbstractResourceManager] --------------------------------------------------------------------------------
[12:50:28]  INFO: [AbstractResourceManager] Setting up themes 'theme_wms' from file 'theme_wms.xml'...
[12:50:28] ERROR: [JAXBUtils] Error in configuration file: 'file:/home/schneider/.deegree/deegree-workspace-utah/themes/theme_wms.xml'
[12:50:28] ERROR: [JAXBUtils] Error: cvc-complex-type.2.4.a: Invalid content was found starting with element 'd:Title'. One of '{"http://www.deegree.org/themes/standard":Identifier, "http://www.deegree.org/themes/standard":Layer, "http://www.deegree.org/themes/standard":Theme}' is expected.
[12:50:28] ERROR: [JAXBUtils] Hint: Try validating the file with an XML-schema aware editor.
[12:50:28] ERROR: [AbstractResourceManager] Could not create resource themes: Could not parse theme configuration file.
[12:50:28] ERROR: [AbstractResourceManager] Cause was: null

It seems that the error message is misleading and that the actual cause is that the affected schema files for the workspace resources contain absolute URLs:

<schema xmlns:t="http://www.deegree.org/themes/standard" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns="http://www.w3.org/2001/XMLSchema"
 targetNamespace="http://www.deegree.org/themes/standard" elementFormDefault="qualified" xmlns:jaxb="http://java.sun.com/xml/ns/jaxb"
 jaxb:version="2.1" xmlns:d="http://www.deegree.org/metadata/description" xmlns:g="http://www.deegree.org/metadata/spatial">

 <import namespace="http://www.deegree.org/metadata/description" schemaLocation="http://schemas.deegree.org/commons/description/3.1.0/description.xsd" />
 <import namespace="http://www.deegree.org/metadata/spatial" schemaLocation="http://schemas.deegree.org/commons/spatialmetadata/3.1.0/spatialmetadata.xsd" />
...
</schema>

[tfr42]

This issue still effects 3.4+ and has an critical impact to every deegree service running in productive environments due to deegree's dependency to schemas.deegree.org.

[dstenger]

This issue seems to not occur anymore.

Used deegree version for testing: 3.4.32

It is possible to start the utah workspace without internet connection (remote ows can, of course, not be initialized). All non-remote-ows resources (not initializing: cascade_demo_deegree_wms, cascade_utah_geology_wms, layer_remotewms_utah_geology, layer_remotewms_utah_springs) initialize correctly and are displayed in the deegree console as active.

Especially, resource theme_wms is initialized correctly. This is due to a change in the schema file which now references the other schema files locally:

<schema xmlns:t="http://www.deegree.org/themes/standard" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns="http://www.w3.org/2001/XMLSchema"
 targetNamespace="http://www.deegree.org/themes/standard" elementFormDefault="qualified" xmlns:jaxb="http://java.sun.com/xml/ns/jaxb"
 jaxb:version="2.1" xmlns:d="http://www.deegree.org/metadata/description" xmlns:g="http://www.deegree.org/metadata/spatial">

 <import namespace="http://www.deegree.org/metadata/description" schemaLocation="../commons/description/description.xsd" />
 <import namespace="http://www.deegree.org/metadata/spatial" schemaLocation="../commons/spatialmetadata/spatialmetadata.xsd" />
...