Feature Request
There's a bunch of scenarios where a call failing to the registry integration is hard to debug. This includes instances where there's a pre-existing shell descriptor for an AAS [1] or the server returns a non-2xx response [2].
Affected code
[1]
|
private boolean shellExistsOnRegistry(String shellId, RegistryAndDiscoveryInterfaceApi registryApi) { |
|
try { |
|
registryApi.getAssetAdministrationShellDescriptorById(shellId); |
|
|
|
return true; |
|
} catch (ApiException e) { |
|
return false; |
|
} |
|
} |
[2]
|
private void registerAas(AssetAdministrationShellDescriptor descriptor) { |
|
RegistryAndDiscoveryInterfaceApi registryApi = aasRepositoryRegistryLink.getRegistryApi(); |
|
|
|
try { |
|
registryApi.postAssetAdministrationShellDescriptor(descriptor); |
|
|
|
logger.info("Shell '{}' has been automatically linked with the Registry", descriptor.getId()); |
|
} catch (ApiException e) { |
|
throw new RepositoryRegistryLinkException(descriptor.getId(), e); |
|
} |
|
} |
Feature Request
There's a bunch of scenarios where a call failing to the registry integration is hard to debug. This includes instances where there's a pre-existing shell descriptor for an AAS [1] or the server returns a non-2xx response [2].
Affected code
[1]
basyx-java-server-sdk/basyx.aasrepository/basyx.aasrepository-feature-registry-integration/src/main/java/org/eclipse/digitaltwin/basyx/aasrepository/feature/registry/integration/RegistryIntegrationAasRepository.java
Lines 169 to 177 in f20e94d
[2]
basyx-java-server-sdk/basyx.aasrepository/basyx.aasrepository-feature-registry-integration/src/main/java/org/eclipse/digitaltwin/basyx/aasrepository/feature/registry/integration/RegistryIntegrationAasRepository.java
Lines 139 to 149 in f20e94d