Error when constraint in template is not binded

[ppazos]

Steps to reproduce

1. Use the GECCO_Personendaten template https://ckm.highmed.org/ckm/templates/1246.169.1134
2. That template uses the openEHR-EHR-CLUSTER.person_birth_data_iso.v0
   archetype, which has some external constraints defined which are not binded with a terminology https://ckm.highmed.org/ckm/archetypes/1246.145.1356
3. Generated a test composition to commit
   GECCO_Personendaten_20210915101000_000001_1.json.txt (note for the corresponding node at0003 of the openEHR-EHR-CLUSTER.person_birth_data_iso.v0 node, there is no terminology to generate the code from, so a random one was generated.

Note: I asked the modelers if the missing terminology bindings shouldn't be in the archetype and then included in the template https://ckm.highmed.org/ckm/#showAComment_1246.160.160_1246.145.1356

Actual result

Result:

{
  "error": "java.lang.IllegalArgumentException",
  "status": "Bad Request"
}

Console log:

2021-09-15 22:12:48.458 WARN 22258 --- [nio-8080-exec-6] o.e.v.constraints.wrappers.CDvCodedText : Constraint reference is not supported, path: /content[openEHR-EHR-ADMIN_ENTRY.person_data.v0]/data[at0001]/items[openEHR-EHR-CLUSTER.person_birth_data_iso.v0]/items[at0003]

Expected result (Acceptance Criteria)

Not sure if this case is supported or the error should say something about the OPT missing some required data, because this might not be an issue of the composition but of the template. Though I don't know if we made any technical design decision around this case.

[ppazos]

@subigre was the reference to the SDK fix commits updated in the EHRBASE POM file?