Open THEvang opened 4 years ago
I think the issue is here:
In the config files I have received, FMU Proxy is spelled fmu-proxy
, not fmuproxy
.
The scheme fmu-proxy is used in libcosim's fmu-proxy uri resolver:
In the above example, there is also the issue of specifying the FMU by GUID and not by name. I don't think the osp-validator is able to find the FMUs modelDescription based on ID. Looks like it uses the name of the FMU.
@THEvang, I assume this issue can be closed as it's fixed?
OSP Validator does not recognise FMUs with fmu proxy is source. For instance,
<Simulator name="vessel_model" source="fmu-proxy://localhost:9090?guid=b71f76f7-b51e-40d5-affb-f63905622e2b" stepSize="0.05"/>
gives the following error message:Exception in thread "main" java.lang.RuntimeException: java.lang.RuntimeException: Unsupported URI schema: 'fmu-proxy' in URI: 'fmu-proxy://localhost:9090?guid=b71f76f7-b51e-40d5-affb-f63905622e2b' . Supported schemas are: [file, fmuproxy] at com.opensimulationplatform.systemstructure.util.DefaultOspModelDescriptionLocator.get(DefaultOspModelDescriptionLocator.java:58) at com.opensimulationplatform.cli.Validator.getModelDescriptionErrorMessages(Validator.java:93) at com.opensimulationplatform.cli.Validator.validate(Validator.java:48) at com.opensimulationplatform.cli.Main.main(Main.java:79) Caused by: java.lang.RuntimeException: Unsupported URI schema: 'fmu-proxy' in URI: 'fmu-proxy://localhost:9090?guid=b71f76f7-b51e-40d5-affb-f63905622e2b' . Supported schemas are: [file, fmuproxy]