Aias00 opened a new issue, #684: URL: https://github.com/apache/rocketmq-dashboard/issues/684
## Problem The Studio backend currently wires `MessageProviderStub` as a production Spring component. Message query and trace endpoints return successful empty results instead of indicating that a real message query provider is not connected. Evidence: - `server/src/main/java/org/apache/rocketmq/studio/instance/message/MessageProviderStub.java` returns `Collections.emptyList()` from `queryMessages`. - The same stub returns an empty trace from `getMessageTrace`. ## Impact This is in the Track 1 / BASE-01 scope. Message query and trace are baseline dashboard capabilities. Returning an empty success response can mislead operators into thinking no message or trace exists. ## Expected Until a real provider is connected, the API should fail explicitly with a structured unsupported/not-implemented response, or route to the real Remoting/Admin implementation when available. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
