Aias00 opened a new issue, #6788: URL: https://github.com/apache/shenyu/issues/6788
- Severity: Medium - Location: `shenyu-client/shenyu-client-websocket/shenyu-client-spring-websocket/src/main/java/org/apache/shenyu/client/spring/websocket/annotation/ShenyuSpringWebSocketClient.java:75`; `.../annotation/ShenyuServerEndpoint.java:80`; `.../init/SpringWebSocketClientEventListener.java:167-182` (`handleClass`) - Description: `ShenyuSpringWebSocketClient` and `ShenyuServerEndpoint` declare `boolean registerMetaData() default false;`. The new autoconfig path consumes this for SpringMvc (`ShenyuSpringMvcClientProcessorImpl.java:44-45`, `SpringMvcApiMetaRegister.java:137-138`, `MateDataApiRegistrarImpl.java:141`), but WebSocket has no processor/extractor in the new register path, and the legacy `SpringWebSocketClientEventListener.handleClass` unconditionally calls `getPublisher().publishEvent(metaData)` for every method without ever reading `registerMetaData`. - Impact: The default `false` signals "do not register metadata", yet metadata is published on every refresh. Users cannot opt out of metadata registration for websocket endpoints; the annotation contract is unimplemented. - Suggested fix: Gate `handleClass` metadata publishing on `beanShenyuClient.registerMetaData()` (and for `@ShenyuServerEndpoint`, read the aliased `registerMetaData`). - Confidence: High --- _Identified during the 2026-08-02 deep re-scan; full list in [`docs/scan2-2026-08-02/06-medium-tiers.md`](docs/scan2-2026-08-02/06-medium-tiers.md)._ -- 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]
