Opening Submodel: Stuck with spinner about basyx-applications HOT 16 CLOSED

We added the possibility to configure CORS in the last release of BaSyx. You can configure it in the context.properties as described here.

from basyx-applications.

Can you please provide more information about the shells which were registered in the Registry. Do they have their own Rest interface or are they only available "offline"? Which Basyx SDK were you using? Another reason for the occurrence of the issue can be multi-AAS from an AAS-repository. Those are currently not supported.

In addition to that, the stuck spinner is fixed in the newest Pull request. If a shell can't be reached a timeout will occur after a short time.

from basyx-applications.

Thank you for the response. I have 4 example AAS in a Basyx repository. I guess that is my problem then. Will re-test with only one.

from basyx-applications.

Update: Stuck with spinner when there is only one AAS in the Basyx registry as well.
I am running Basyx aas server and registry Docker containers. Registry and servers are backed by MongoDB databases.

from basyx-applications.

Can you access said AAS through your browser by entering it's URL? Is the port of the Docker container exposed to be accessed from outside the container?

It would be helpful to provide some more information to exactly reproduce your issue. maybe a step by step description what you did to run into the issue.

from basyx-applications.

I think I found the issue and it seems to have to do with AAS repositories in general. I tested this with the dotnet sdk MultiAssetAdministrationShell example and ComplexAssetAdministrationShellScenario. When I try to retrieve the shell(s) I get this response:

I will try to fix the code in the examples of the Dotnet SDK and try again if the GUI works.

But I definitely think the GUI is not the issue. In the meantime you could try to use AAS which are directly registered in the registry and not part of an AAS repository.

from basyx-applications.

Thank you for all your guidance. I think I see the problem on my side. Probably some bad config inside my container(s). It uses localhost:4001 addresses for the endoints:

If the GUI reads those endpoints and try to access them it will fail of course!
I will try to find the correct parameters and update.

from basyx-applications.

You are welcome :) Hopefully you can fix the problem and use the GUI afterwards.

from basyx-applications.

Hello, I encountered the same problem when showing submodel details in GUI. I can access my AAS server, see this AAS well registered in the registry server and see this AAS appearing in GUI. However, the submodel information doesn't appear in GUI. I would like to ask how did you solve this spinning problem? Thank you in advance.

from basyx-applications.

This seems to be an issue related to the configuration of the registry. First of all, is there a reason you access the registry this way 127.0.0.1:8082/registry instead of this way 127.0.0.1:8082? I think that's the proposed way to do it but I will definitely test your implementation to check if that could be the reason for the problem.

Just for your information how the GUI works: It takes the first endpoint address and tries to reach the Asset Administration shell with that URL. You could try to copy that exact address and open it in another tab. If that works the GUI should work to.

Hope that helps :)

from basyx-applications.

Thank you for your response. I tried with different endpoints but it still not work. Even when I followed exactly the steps shows in this tutorial, I couldn't access to the submodel information by GUI.
https://wiki.eclipse.org/BaSyx_/_Introductory_Examples_/_Java_/_Step_5

from basyx-applications.

Alright, I see. Didn't even know this tutorial existed. I am working with the C# SDK normally but Java should also work with no problems. The GUI was tested against every SDK with a rest interface.

Can you show me some screenshots from the Basyx UI's (http://localhost:8082/registry/ui and http://localhost:8081/aasServer/ui)?

from basyx-applications.

Please also check the request send from your browser (press F12 then open network tab).

A screenshot like this would also be helpful:

from basyx-applications.

Here's the screenshot that connnect to the registry (work)

Screenshot of discovering submodels (not work)

I used the registry server and gui server from docker, and the /registry/ui is not working from my side.

from basyx-applications.

Thank you for your help, I added a CROS plugin in my navigator and it works! :)

from basyx-applications.

Oh well. CORS was the Problem... That's annoying. I thought CORS would not affect the localhost. This is getting more restrictive every month I feel.

from basyx-applications.