-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Submodel element values serialization when getting "/values" still not working #158
Comments
Would it be possible to provide an example AAS (e.g., as AASX) so that we can take a look at it? |
Yes for sure, here is my example AAS as json:
And here the Nameplate submodel:
And I want to retrieve the nameplate-submodel in a minimized version with /values. Here is my request: But the response is:
|
The submodel JSON is not consistent with the schema defined in Details of the AAS Part 1 V2.0.1.
If you remove the "langstring" entry in the MultiLanguageProperties value, everything is working correctly. Did you create this JSON with the AASX Package Explorer or by hand/in a proprietary way? |
No, I did create it by hand. Can you maybe give me an example for a right configured MultiLanguageProperty? It still is not working when deleting the "langstring" key. |
The following stripped down submodel illustrates how to adapt the MLP:
|
Thank you, now it is working. Can you maybe say if this /values endpoint is also available for a first draft of the BillOfMaterial-submodel? |
Yes, it should work |
Okay, this sounds very interessting for me because retrieving a minimzed version of the BillOfMaterial-Submodel is exactly our use-case. With this instance it is unfortunaley not working: `
Maybe do you have here also an clue why the /values is not working? |
Thanks for pointing this out, there's a bug regarding statements right now in BaSyx. For now, you can circumvent triggering this by using "statement" instead of "statements". However, due to this, the "/values" serialization of a Statement is not handled correctly. I will create separate issues for this and update them accordingly. |
Can be closed upon resolving eclipse-basyx/basyx-java-sdk#158 and eclipse-basyx/basyx-java-sdk#159 |
Both issues are resolved. The fixes are already available on the development branch and will be integrated in the next release |
I tried the /values-Endpoint with another submodel which is the SoftwareNameplate-Submodel. Unfortunately it is not working and I am getting a 500 error. Here is my submodel:
Can you maybe say me what is the problem with the submodel? |
Thank you! Now /values is working. |
I think you're mixing up the JSON schema and the actual json instance. The correct modeling of the valueType is as follows:
|
Thank you. Unfortunately with this declaration the /values-endpoint is not working anymore. Our value is in the format "2021-01-01", is this a known issue? |
Would it be possible to provide a complete Submodel example? Then, I will take a look at the issue and come back to you. |
Yes for sure, for example for the TechnicalData-submodel:
The FurtherInformation.ValidDate property is right now modeled with and then the /values endpoint is not working anymore. If I change it back to "string", the /values endpoint is working. |
Thanks a lot! I could reproduce the issue. There's a bug with date in BaSyx, you can avoid it by using dateTime instead. |
I've added an issue in the SDK repository: eclipse-basyx/basyx-java-sdk#190 |
Perfect, thank you for the information :) |
In release 1.2.0 the release notes said, that the bug "Fixes submodel element values serialization when getting "/values"" is solved. But after testing the new release the /values is still not working or only for some very certain submodels.
I am using this command: /shells/{aasId}/aas/submodels/{submodelIdShort}/submodel/values. In my case it only works with the TechnicalData-submodel. But that was already the case at the release 1.0.0. So it looks like that there is no improvement for this topic.
The text was updated successfully, but these errors were encountered: