Comments (8)
Hi Björn,
the issue you faced was indeed a bug.
We fixed it with the PR mentioned above.
Until the docker images are getting updated you can build the Images with the latest bug fix yourself when the PR is merged.
from basyx-java-server-sdk.
Hi Björn,
your first request should have worked to a add a new SE to an existing SEC.
Could you please attach a minimal example containing your config files (properties, docker-compose, AASX files), so we can reproduce the issue?
Thanks in advance,
Mateus
from basyx-java-server-sdk.
I use the example component and have only released the ports for mongo in the dockercompose.yml. I think I also deleted all docker images beforehand to make sure that an old one is not used during the installation.
Starting the docker-compose works fine with "docker-compose up -d" and all components are running healthy.
All my http commands i send via postman
from basyx-java-server-sdk.
I assemble my AAS, the submodel and the SEMC etc. as follows:
http-POST: http://localhost:8081/shells (works)
body:
{
"idShort": "testAas",
"id":"testAasId"
}
http-POST: http://localhost:8081/submodels (works)
body:
{
"idShort": "testSubmodel",
"id":"testSubmodelId"
}
http-POST: http://localhost:8081/shells/dGVzdEFhc0lk/submodel-refs (works)
Body:
{
"keys": [
{
"type": "Submodel",
"value": "testSubmodelId"
}
],
"type": "ModelReference"
}
http-Post: http://localhost:8081/submodels/dGVzdFN1Ym1vZGVsSWQ=/submodel-elements (works)
{
"idShort": "ExampleSEMC",
"modelType": "SubmodelElementCollection"
}
http-Post:
http://localhost:8081/submodels/dGVzdFN1Ym1vZGVsSWQ=/submodel-elements/ExampleSEMC (http status 201 but its again at the wrong level and not inside “ExampleSEMC”)
{
"idShort": "ExampleProp",
"modelType": "Property"
}
from basyx-java-server-sdk.
I have the same problem using the latest BaSyx AAS Environment Docker image:
Executing an HTTP post to {{Endpoint}}/submodels/{{SubmodelId}}/submodel-elements/Segments.InternalSegment.Records will always add the element passed in the request body as a top-level element as direct child of the submodel instead of as a child of ...Records.
HTTP get to the above adress works fine so the idShort-Path should be correct.
The same problem exists even when posting to {{Endpoint}}/submodels/{{SubmodelId}}/submodel-elements/Segments, i.e. when an idShort-Path with only one element is used.
from basyx-java-server-sdk.
@FriedJannik I used the current version of the 2.0.0-SNAPSHOT build of the eclipsebasyx/aas-environment
component. However, I am still experiencing the same problems as described above. As the image was updated yesterday, I guess that it should already contain this fix?
from basyx-java-server-sdk.
Hi @de-ich,
to use the new docker image, you have to remove the old image first, as the Version Tag is not changed, so docker does not automatically pull the new version.
I just checked it, and for me it works just fine.
Let me know if you need any further help :)
from basyx-java-server-sdk.
@FriedJannik I did delete the old image first so I am using the new image aswell. However, now that I know that it should work, I will investigate further and try to provide a minimum working example.
from basyx-java-server-sdk.
Related Issues (20)
- Invoking /shells with invalid asset ids returns 500 HOT 3
- No 'aasx-spec' document found in .aasx HOT 6
- Improvements on BaSyx delegation feature HOT 1
- Unable to Retrieve AAS from MongoDB HOT 3
- Incosistent naming of Enums in openAPI-spec and returned bodies HOT 6
- No MQTT Events send when changing MLPs HOT 6
- No MQTT events for PUT-Requests? HOT 7
- Unable to retrieve list of AAS Identifiers from MongoDB in Discovery HOT 3
- cant connect my aasx file to the registry HOT 1
- Issue with Invokable Operation for File Input in Submodel HOT 6
- Bug: basyx.aasenvironment+MongoDB stores binaries in Memory anyways (and by extension basyx.aassubmodelregitry as well i guess) HOT 3
- Issue : Unexpected Error 500 Occurred After using Blob input HOT 1
- Discovery service startup error when starting with MongoDB instead of InMemory HOT 2
- Invoking /shells?cursor=x returns 500 HOT 2
- Invoking /shells/$reference returns 400 HOT 2
- Problem with Adding DataBridge to Docker-Compose File HOT 5
- Submodel Repository returns empty embeddedDataSpecificatios for SubmodelElements HOT 1
- Dependency to license-tool-plugin:1.1.1-SNAPSHOT makes it hard to build out-of-the-box HOT 6
- move org.eclipse.digitaltwin.basyx.core.LoggingPropertySourceLoader to new artifact basyx.springcore - would help to reduce dependencies to basyx.core HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from basyx-java-server-sdk.