Currently the Production Planner returns with HTTP status 500 (Internal Server Error) and no error message, if the planning process fails. This is due to a deliberate throwing of a RuntimeException, if a planning failure occurs (thereby causing a rollback of the database transaction).
The Production Planner shall be reworked so that it can return a proper HTTP status (e. g. 400 Bad Request) and a formatted error message according to the prosEO standard in the Warning header, while still being able to roll back the database transaction.
Currently the Production Planner returns with HTTP status 500 (Internal Server Error) and no error message, if the planning process fails. This is due to a deliberate throwing of a RuntimeException, if a planning failure occurs (thereby causing a rollback of the database transaction).
The Production Planner shall be reworked so that it can return a proper HTTP status (e. g. 400 Bad Request) and a formatted error message according to the prosEO standard in the Warning header, while still being able to roll back the database transaction.