Closed jongunee closed 1 year ago
I am not able to understand or reproduce your problem as the description is not clear to me and seems to be wrong or missing crucial information.
Regarding the converted JSON, I don't see any bug here as both examples (before & after conversion) are exactly the same and both have language
and text
property set to null so FA³ST Service returning null seems to be the correct and expected behavior.
For issues regarding FA³ST Service please refer to the corresponding repository at https://github.com/FraunhoferIOSB/FAAAST-Service.
But I can already tell you that FA³ST Service by default only starts an HTTP endpoint, so if you want to also have a OPC UA endpoint to need to explicitely specify this via the configuration file or via command-line paramter (--endpoint OPCUA
for having only a OPC UA endpoint and no HTTP endpoint, --endpoint HTTP,OPCUA
for having both at the same time).
Please provide a more detailed explanation of your problem, in this case including an expected version of the JSON document or at least a description of what you think is wrong with it.
Sorry, i uploaded wrong json file
json file before converting
...
{
"value": {
"langString": [
{
"language": "en",
"text": "SBOI"
}
]
},
"semanticId": {
"keys": [
{
"type": "ConceptDescription",
"local": true,
"value": "0173-1#02-AAW338#001",
"index": 0,
"idType": "IRDI"
}
]
},
"constraints": [],
"hasDataSpecification": [],
"idShort": "ManufacturerProductDesignation",
"category": "PARAMETER",
"modelType": {
"name": "MultiLanguageProperty"
},
"kind": "Instance"
},
...
json file after converting
...
{
"modelType": {
"name": "MultiLanguageProperty"
},
"kind": "Instance",
"semanticId": {
"keys": [
{
"idType": "Irdi",
"type": "ConceptDescription",
"value": "0173-1#02-AAW338#001"
}
]
},
"category": "Parameter",
"idShort": "ManufacturerProductDesignation",
"value": [
{
"language": null,
"text": null
}
]
},
...
as you can see, i expected value SBOI
, but after converting it shows null
can you check one more?
Thank you for the update. I now see the problem you are describing. However, when trying to reproduce the problem by copying your JSON snippet in a simple model file I did not encounter the problem. Could you please provide a whole JSON file that I can use to reproduce the problem?
Thank you! i uploade it below
I could reproduce and pinpoint the issue. Problem was, that AASX Package Explorer uses a non-standard-compliant format for serializing MultiLanguageProperty
. Not sure why I couldn't reproduce it with the initial snippet provided but with the full example it now works.
If you have been using the precompiled JAR, please checkout the latest version of the main branch and compile it yourself until a new version will be released.
If this fixes the problem, please close this issue, otherwise let me know.
Great it works!!
Thanks :)
Describe the bug A clear and concise description of what the bug is.
To Reproduce Steps to reproduce the behavior:
FAAAST-Package-Explorer-Converter
for using inFAAAST-Service
FAAAST-Service
with converted json fileExpected behavior
FAAAST-Service
is working wellOutput
FAAAST-Service
MultiLanguageProperty
shows null.json file before converting
json file after converting
Additional context
I am wondering why opc ua endpoint is not opened and whether you are not support MultiLanguageProperty.
Thanks!