Stream: committers
Topic: Build error FHIRException: Unable to find type string
Rik Smithies (Mar 12 2020 at 14:10):
I am trying to change an attribute
from Coding|Quantity|string|date|boolean|Attachment
to CodeableConcept|Quantity|date|boolean|Attachment
and getting a strange build error.
[java] Caused by: org.hl7.fhir.exceptions.FHIRException: Unable to find type string for element valueString with path ManufacturedItemDefinition.characteristic.value[x]
But there is no longer a string there. It is as if it is remembering that it had a string in it from before the change. Why might that be?
If I put back the string it says Unable to find type Coding (which is also no longer there).
Lloyd McKenzie (Mar 12 2020 at 14:39):
There may be mappings that have to be updated to deal with the change to the resource. Can you provide the full stack trace?
Rik Smithies (Mar 12 2020 at 15:22):
no mappings, bindings or search parameters.
Rik Smithies (Mar 12 2020 at 15:23):
this is trace I get
[java] This was a Partial Build 0.398 267sec 1025MB
[java] Build: manufactureditemdefinition 0.0 267sec 1025MB
[java] java.lang.Exception: processing manufactureditemdefinition-example
[java] at org.hl7.fhir.tools.publisher.Publisher.produceResource2(Publisher.java:4165)
[java] at org.hl7.fhir.tools.publisher.Publisher.produceSpec(Publisher.java:2404)
[java] at org.hl7.fhir.tools.publisher.Publisher.produceSpecification(Publisher.java:2217)
[java] at org.hl7.fhir.tools.publisher.Publisher.execute(Publisher.java:625)
[java] at org.hl7.fhir.tools.publisher.Publisher.main(Publisher.java:486)
[java] Caused by: org.hl7.fhir.exceptions.FHIRException: Unable to find type Coding for element valueCoding with path ManufacturedItemDefinition.characteristic.value[x]
[java] at org.hl7.fhir.r5.elementmodel.Property.getChildProperties(Property.java:312)
[java] at org.hl7.fhir.r5.elementmodel.XmlParser.parseChildren(XmlParser.java:242)
[java] at org.hl7.fhir.r5.elementmodel.XmlParser.parseChildren(XmlParser.java:333)
[java] at org.hl7.fhir.r5.elementmodel.XmlParser.parseChildren(XmlParser.java:333)
[java] at org.hl7.fhir.r5.elementmodel.XmlParser.parse(XmlParser.java:179)
[java] at org.hl7.fhir.r5.elementmodel.XmlParser.parse(XmlParser.java:163)
[java] at org.hl7.fhir.r5.elementmodel.XmlParser.parse(XmlParser.java:135)
[java] at org.hl7.fhir.r5.elementmodel.Manager.parse(Manager.java:57)
[java] at org.hl7.fhir.tools.publisher.Publisher.processExample(Publisher.java:4623)
[java] at org.hl7.fhir.tools.publisher.Publisher.produceResource2(Publisher.java:4163)
[java] ... 4 more
Rik Smithies (Mar 12 2020 at 15:24):
maybe it is validating the example that is failing
Lloyd McKenzie (Mar 12 2020 at 15:25):
Nope. The issue is that certain types of changes to the resource require a new push of the HAPI reference implementation. This appears to be one of them. @Grahame Grieve
Rob Hausam (Mar 12 2020 at 15:26):
Yes. I ran into that when making changes to ConceptMap.
Rik Smithies (Mar 12 2020 at 15:30):
ah ok, thanks. it only seems to affect some attributes. Maybe it is when there's some combination of choices. Straight change of Coding to CodeableConcept, or Coding|Reference to CodeableReference doesn't seem to trigger it.
Rik Smithies (Mar 12 2020 at 15:31):
So what is the fix? I can just roll back, but then HAPI won't ever get updated. Is it a case of waiting for a build fix?
Lloyd McKenzie (Mar 12 2020 at 19:33):
Build fix
Grahame Grieve (Mar 12 2020 at 20:51):
nah this isn't one of them. that only happens to core conformance resources
Grahame Grieve (Mar 12 2020 at 20:52):
this one looks to me like you still have an example using a string
Rik Smithies (Mar 12 2020 at 23:39):
yes, thanks it was the example. Odd error, but now that I know :-)
Last updated: Apr 12 2022 at 19:14 UTC
