class basyx::server::TCPServer<IntegrationTestModelProvider>' has no member named 'update'

[akoscsiszar]

When following the cpp_test_server intergration test, as an exampe to create a simple BaSyx Server, there is a compilation error, stating, that the TCPServer does not have an 'update' memeber. Upon checking the header n in include/BaSyx/server/TCPServer.h one can see that the TCPServer does not have an 'update' member. However, in the CI it does not seem, that any test is failing

Does the TCPServer intergration test actually pass, or is it not run, due to the BASYX_BUILD_INTEGRATION_TESTS flag in tests/CMakeLists.txt

Is there a reason why integration tests are skipped? Is there any guidance/documentation on creating a BaSyx Server, other then the described integrationt test?

[IESE-T3]

Hello,

thank you for bringing this issue to our attention.

Those integration tests were used to test the internal communication with the BaSyx Java SDK, back when both SDKs were hosted in the same repository on the old infrastructure.
Currently those tests are not needed anymore, and we have since then shifted away from the proprietary VAB protocol, the TCPServer in question did use (meaning the TCPServer does not offer the REST API of the AAS as defined by the Platform I4.0).

All development of the C++ SDK has currently shifted to the development_v2 branch, which will have its own REST server. Announcements and Documentation of the new version will follow in the coming weeks, so please keep an eye out for that.

Best regards

[akoscsiszar]

Thank you for the reply!

It there a way quick to set up a C++ AAS with 3-4 float parameters and register to the Basyx Registry available on Docker Hub? I took a look at the test on the mentioned branch, is seems that creating the properties is straight forward, but I am having trouble finding a way to start a "server" and register to the Basyx AAS Registry.

Thanks!

[IESE-T3]

Hello!

The REST server will be published in https://github.com/eclipse-basyx/basyx-cpp-components , since we are planning a split between the metamodel implementation of the SDK, and components being built upon that metamodel as a foundation, so people who do not want to use our components, can decide to build their own using just our provided metamodel.

Currently, the REST server is stuck in migration, but depending on your needs I can try to reshuffle my plans and get it published sooner.

How quickly would you need it?

[akoscsiszar]

It would be nice to have it running in a week, otherwise we will use a different solution.