[BUG] Different behaviour of AAS Discovery Service (standalone) and AAS Discovery Service of DigitalTwin Registry

[seicke]

Describe the bug
/lookup/shells of not available AAS ID yields different response.

To Reproduce

1. docker compose up

# $docker compose up -d
name: basyx-server-test

services:

  basyx-aas-discovery-dev:
    image: eclipsebasyx/aas-discovery:2.0.0-SNAPSHOT
    container_name: basyx-aas-discovery-dev
    restart: always
    environment:
      SERVER_PORT: ${BASYX_AAS_DISCOVERY_PORT:-8081}
      SERVER_SERVLET_CONTEXT_PATH: /

      SPRING_APPLICATION_NAME: AAS Discovery Service
      BASYX_AASDISCOVERYSERVICE_NAME: aas-discovery-service

      BASYX_BACKEND: InMemory
      
      BASYX_CORS_ALLOWED_ORIGINS: '*'
      BASYX_CORS_ALLOWED_METHODS: GET,POST,PATCH,DELETE,PUT,OPTIONS,HEAD
    ports:
      - ${BASYX_AAS_DISCOVERY_PORT_PUBLISHED:-9985}:${BASYX_AAS_DISCOVERY_PORT:-8081}
    networks:
      - basyx_network

  basyx-dt-registry-dev:
    image: eclipsebasyx/digitaltwinregistry:2.0.0-SNAPSHOT
    container_name: basyx-dt-registry-dev
    restart: always
    environment:
      SERVER_PORT: ${BASYX_DT_REGISTRY_PORT:-8081}
      SERVER_SERVLET_CONTEXT_PATH: /

      SPRING_APPLICATION_NAME: Digital Twin Registry

      BASYX_BACKEND: InMemory

      BASYX_CORS_ALLOWED_ORIGINS: '*'
      BASYX_CORS_ALLOWED_METHODS: GET,POST,PATCH,DELETE,PUT,OPTIONS,HEAD
    ports:
      - ${BASYX_DT_REGISTRY_PORT_PUBLISHED:-9984}:${BASYX_DT_REGISTRY_PORT:-8081}
    networks:
      - basyx_network

networks:
  basyx_network:
    name: basyx_network
    driver: bridge

2a. http://localhost:9985/lookup/shells/aHR0cHM6Ly9leGFtcGxlLmNvbS9pZHMvQXNzZXRBZG1pbmlzdHJhdGlvblNoZWxsLzc5MDZfNzA3OF82ODU5XzE4OTQ
(eclipsebasyx/aas-discovery:2.0.0-SNAPSHOT)
HTTP 404 response with payload

[
  {
    "code": 404,
    "messageType": "Error",
    "correlationId": "AssetLinkDoesNotExistException-404",
    "text": "Asset link for shell Id https://example.com/ids/AssetAdministrationShell/7906_7078_6859_1894 does not exist",
    "timestamp": "..."
  }
]

2b. http://localhost:9984/lookup/shells/aHR0cHM6Ly9leGFtcGxlLmNvbS9pZHMvQXNzZXRBZG1pbmlzdHJhdGlvblNoZWxsLzc5MDZfNzA3OF82ODU5XzE4OTQ
(eclipsebasyx/digitaltwinregistry:2.0.0-SNAPSHOT)
HTTP 404 response without payload

Expected behavior
Same response behaviour of AAS Discovery Service (standalone) and AAS Discovery Service of DigitalTwin Registry

[aaronzi]

Agreed, 2b should look like 2a. I will add this to our backlog since this is no functional issue and does not break the usability.