Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to Software Development on Codidact!

Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.

Comments on Validating xsd schema that contains import from external http source in Java 11

Post

Validating xsd schema that contains import from external http source in Java 11

+2
−0

In the example.xsd file I have an import to an external xsd file that looks like this:

<schema xmlns="http://www.w3.org/2001/XMLSchema"
        targetNamespace="http://test.example.com"
        xmlns:wsi="http://ws-i.org/profiles/basic/1.1/xsd">
<import namespace="http://ws-i.org/profiles/basic/1.1/xsd" 
        schemaLocation="http://ws-i.org/profiles/basic/1.1/swaref.xsd" />
<element name="attachment" type="wsi:swaRef" />
</schema>

In the config file I have created the XsdSchema and validator beans

@Bean
public XsdSchema schema() {
  return new SimpleXsdSchema(new ClassPathResource("example.xsd"));
}

@Bean
public XmlValidator schemaValidator(XsdSchema xsdSchema) {
  return xsdSchema.createValidator()); // throws exception
}

when starting the server I get the following exception:

schema_reference: Failed to read schema document 'swaref.xsd', because 'http' access is not allowed due to restriction set by the accessExternalSchema property.

In order to solve the problem I have tried different things such as:

  • Setting System.setProperty("javax.xml.accessExternalSchema", "all");
  • Setting System.setProperty("javax.xml.accessExternalDTD", "all");
  • Creating jaxp.properties file under both jdk/lib and jdk/jre/lib and adding javax.xml.accessExternalSchema = all in there
  • Changing import in xsd to <import namespace="http://ws-i.org/profiles/basic/1.1/xsd"/> which then causes different exception - Cannot resolve the name 'wsi:swaRef' to a(n) 'type definition' component.

Java 11, Gradle 5.5.1, Spring Boot 2.1.6, jaxws-ri 2.3.2

how to get it to work?

History
Why does this post require moderator attention?
You might want to add some details to your flag.
Why should this post be closed?

1 comment thread

General comments (3 comments)
General comments
Monica Cellio‭ wrote over 3 years ago

Hello. Apparently we have a bug that affected the layout on this post (made things kind of unreadable). I'm trying to get that fixed, but in the meantime I made an edit that I believe is harmless but want to check. In the first code block, I moved each attribute to its own line instead of having multiples on single (longer) lines. I'm pretty sure XSD doesn't care about whitespace, but if I'm wrong, please accept my apologies.

Peter Taylor‭ wrote over 3 years ago

Not an answer because I don't have a test environment to see whether it works, but have you tried (a) javax.xml.accessExternalSchema = http in jaxp.properties; (b) searching all files for other references to javax.xml.accessExternalSchema which might have priority; (c) logging System.getProperty("javax.xml.accessExternalSchema") to check that the jaxp.properties is being loaded?

Janar‭ wrote over 3 years ago · edited over 3 years ago

@Monica Cellio yes, that's fine, thank you

@Peter Taylor yes, I have even tried setting the system property right before the createValidator call.