Skip to content
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

Registry-Integration Component: registry-integration #424

Open
mateusmolina-iese opened this issue Sep 3, 2024 · 0 comments
Open

Registry-Integration Component: registry-integration #424

mateusmolina-iese opened this issue Sep 3, 2024 · 0 comments

Comments

@mateusmolina-iese
Copy link
Contributor

mateusmolina-iese commented Sep 3, 2024

Design Considerations

  1. We should know where to save each shell
  • InMemory
  • MongoDB
  1. Shells and Registries should be kept in sync
  • HttpPollingConsumer (see databridge)
  • Mqtt Eventing

Rules

  • ConnectedAasEnvironment als dep
  • In basyx.components (new folder in root)
  • Existing implementation of registry-integration stays on the repository
  • Registries should be specified (RegistrySpecification) as either a tuple of AasRegistry and SmRegistry or a single AasRegistry (smDescriptor will be saved in the AasRegistry)

Acceptance Criteria

  • Should allow configuration of multiple registries
  • Should allow the specification of additional registries via a REST endpoint. E.g.:
    createConnectedAas(Aas, RegistrySpecification)
    createConnectedSubmodel(Submodel, RegistrySpecification)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: BaSyx Java V2
Development

No branches or pull requests

1 participant