You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a developer or API user, I want the API to provide clear and meaningful error responses so that I can understand whether a feature is not implemented or there is an issue with the backend, and take appropriate action.
Rules
When a feature is not implemented for an endpoint but the spec/interface includes it, the response when using it should reflect this
When there is a problem in the backend, the response should include a meaningful response (not just internal server error 500 response)
analyze, where exceptions are "just" passing the the stack trace, try throwing a more specific exception or if it is a runtime exception, add a more specific Error description
For each endpoint all known errors are handled with meaningful error messages and http status
Risks and Assumptions
Message handling for error responses should be part of common
Error messages should be meaningful, but should not provide insight into the codebase
how would just an exception be decoded to a useful message -> providing the message is more problematic -> mapping between exception and Message needed
Http status is translated to its actual meaning
Error Message that is provided by java is enough in the first place
(Translation from Java error message to meaningful error message is out of scope)
As a developer or API user, I want the API to provide clear and meaningful error responses so that I can understand whether a feature is not implemented or there is an issue with the backend, and take appropriate action.
Rules
Entry Points
Acceptance Criteria
For each endpoint all known errors are handled with meaningful error messages and http status
Risks and Assumptions
References & Notes
https://github.com/eclipse-basyx/basyx-java-server-sdk/blob/main/basyx.aasregistry/basyx.aasregistry-service/src/main/java/org/eclipse/digitaltwin/basyx/aasregistry/service/errors/BasyxControllerAdvice.java
This is the package for messages:
org.eclipse.digitaltwin.basyx.aasregistry.model.Message
Dependencies and Blockers
The text was updated successfully, but these errors were encountered: