Stream: implementers
Topic: Validating a URL
Charlie Filkins (Sep 24 2020 at 18:40):
Folks,
I'm trying to validate a resource using a URL, but get the following. Any suggestions as to what I'm doing wrong?
Thanks ... Charlie
-->java -jar ../FHIR/Validators/HL7/5.1.13/validator-cli.jar -version 4.0 http://hapi.fhir.org/baseR4/Patient/1138453
FHIR Validation tool Version 5.1.13 (Git# 268bb8cde75c). Built 2020-09-21T19:41:41.329Z (70 hours old)
Java: 13.0.2 from /Library/Java/JavaVirtualMachines/jdk-13.0.2.jdk/Contents/Home on x86_64 (64bit). 4096MB available
Paths: Current = /Users/a552246/Documents/InterOp/Examples, Package Cache = /Users/a552246/.fhir/packages
Params: -version 4.0 http://hapi.fhir.org/baseR4/Patient/1138453
Loading
Load FHIR v4.0 from hl7.fhir.r4.core#4.0.1 - 4575 resources (00:05.0646)
Terminology server http://tx.fhir.org - Version 1.0.353 (00:01.0373)
Get set... go (00:00.0027)
Validating
Validate http://hapi.fhir.org/baseR4/Patient/1138453 ..Detect format for http://hapi.fhir.org/baseR4/Patient/1138453
Exception in thread "main" org.hl7.fhir.exceptions.FHIRException: Unable to find/resolve/read -ig http://hapi.fhir.org/baseR4/Patient/1138453
at org.hl7.fhir.validation.ValidationEngine.fetchFromUrl(ValidationEngine.java:656)
at org.hl7.fhir.validation.ValidationEngine.loadIgSource(ValidationEngine.java:538)
at org.hl7.fhir.validation.ValidationEngine.loadContent(ValidationEngine.java:1139)
at org.hl7.fhir.validation.ValidationEngine.validate(ValidationEngine.java:1296)
at org.hl7.fhir.validation.cli.services.ValidationService.validateSources(ValidationService.java:66)
at org.hl7.fhir.validation.Validator.main(Validator.java:212)
Lloyd McKenzie (Sep 24 2020 at 19:17):
@Grahame Grieve
Grahame Grieve (Sep 24 2020 at 21:12):
hmm. fixed next release
Charlie Filkins (Sep 25 2020 at 11:52):
Thanks gentlemen. @Grahame Grieve, when you say next release, do you mean 5.1.14 or something newer than that? I validated with 5.1.14 and received the same error.
Thanks ... Charlie
Grahame Grieve (Sep 25 2020 at 15:20):
5.1.15
Charlie Filkins (Sep 25 2020 at 16:11):
Excellent ... Thank you!
Charlie Filkins (Sep 29 2020 at 12:04):
@Grahame Grieve Using 5.1.15 of the Validator, I still receive the same message "Unable to find/resolve/read -ig" Could this be problems related to HTTP proxies?
Thanks ... Charlie
Grahame Grieve (Sep 29 2020 at 21:07):
don't know. do you get any other output?
Charlie Filkins (Sep 29 2020 at 21:59):
Here you go ...
-->java -jar ../FHIR/Validators/HL7/5.1.15/validator_cli.jar -version 4.0 http://hapi.fhir.org/baseR4/Patient/1138453
FHIR Validation tool Version 5.1.15 (Git# 5bb59c3b8265). Built 2020-09-26T00:16:14.10Z (3 days old)
Java: 13.0.2 from /Library/Java/JavaVirtualMachines/jdk-13.0.2.jdk/Contents/Home on x86_64 (64bit). 4096MB available
Paths: Current = /Users/xxx/Documents/InterOp/Examples, Package Cache = /Users/xxx/.fhir/packages
Params: -version 4.0 http://hapi.fhir.org/baseR4/Patient/1138453
Loading
Load FHIR v4.0 from hl7.fhir.r4.core#4.0.1 - 4575 resources (00:04.0436)
Terminology server http://tx.fhir.org - Version 1.0.353 (00:01.0052)
Get set... go (00:00.0003)
Validating
Validate http://hapi.fhir.org/baseR4/Patient/1138453 ..Detect format for http://hapi.fhir.org/baseR4/Patient/1138453
Exception in thread "main" org.hl7.fhir.exceptions.FHIRException: Unable to find/resolve/read -ig http://hapi.fhir.org/baseR4/Patient/1138453
at org.hl7.fhir.validation.ValidationEngine.fetchFromUrl(ValidationEngine.java:656)
at org.hl7.fhir.validation.ValidationEngine.loadIgSource(ValidationEngine.java:538)
at org.hl7.fhir.validation.ValidationEngine.loadContent(ValidationEngine.java:1139)
at org.hl7.fhir.validation.ValidationEngine.validate(ValidationEngine.java:1296)
at org.hl7.fhir.validation.cli.services.ValidationService.validateSources(ValidationService.java:66)
at org.hl7.fhir.validation.Validator.main(Validator.java:212)
Grahame Grieve (Sep 29 2020 at 22:16):
hmm maybe it is a proxy/cache issue. I don't understand that stack at all
Grahame Grieve (Sep 29 2020 at 22:23):
I added some more debugging for next release
Last updated: Apr 12 2022 at 19:14 UTC
