Error message shown when trying to select an axis value in the Logical Definition tab for an axis that has no value set specified

[csnyulas]

This issue is to document an error 500 that we were getting when trying to select an axis value in the Logical Definition tab, when editing the logical definition or the necessary conditions, for an axis that has no value set specified, such as Serotype or "Genomic and Chromosomal Anomaly⁠" and Measurement (which should in fact have had an value set specified).

These exceptions should be caught and a more user friendly message should be shown, and continue to prevent the user from editing values for such axis.

[csnyulas]

This has been fixed, and now a user friendly message is shown for the axes that have no value set configured, providing a better UX.

@alexsilaghi please link to the code fixing this an you can close it. However, if we would have the same behavior activated also for the postcoordination axis value selection widgets in the Postcoordination tab, it would be even better. Could we have that implemented that as part of this ticket, or should we open a new issue for that?

As a side note: As part of the third point of #367 we also configured the http://id.who.int/icd/schema/measurement⁠ axis to have value set http://id.who.int/icd/entity/112199345, which helps reduce the number of axes where this message will be shown.

[alexsilaghi]

for logical definition : protegeproject/webprotege-gwt-ui@b7a4abe

[alexsilaghi]

fixed for postcoordination in : protegeproject/webprotege-gwt-ui@004ae24