Aias00 opened a new issue, #6682: URL: https://github.com/apache/shenyu/issues/6682
- Severity: High - Location: `shenyu-client/shenyu-client-dubbo/shenyu-client-apache-dubbo/src/main/java/org/apache/shenyu/client/apache/dubbo/processor/extractor/ServiceProcessor.java:25` (import), `:40-42` (process); `shenyu-client/shenyu-client-dubbo/shenyu-client-apache-dubbo/src/main/java/org/apache/shenyu/client/apache/dubbo/ApacheDubboApiBeansExtractor.java:21,33` (extractor uses Dubbo's `@Service`) - Description: `ApacheDubboApiBeansExtractor` correctly imports `org.apache.dubbo.config.annotation.Service` (Dubbo's deprecated `@Service`) and registers it as a supported annotation. But `ServiceProcessor` imports `org.springframework.stereotype.Service` (Spring's generic `@Service`) and types itself `ApiAnnotationProcessor<Service>` with `matchAnnotation()` returning Spring's `Service.class`. A bean annotated with Dubbo's `@Service` (or `@ShenyuService` which meta-annotates it) does NOT carry Spring's `@Service`, so `ApiAnnotationProcessor.getAnnotation(apiBean)` always returns null, and `process(apiBean, annotation)` is never invoked. The beanPath is never set (stays `""` default). - Impact: In the ApiBean-based extraction path, old-style `@Service`/`@ShenyuService` Dubbo beans produce metadata with missing path components (only contextPath + methodName, no service path). The gateway routes to wrong paths. - Suggested fix: Change `ServiceProcessor` import from `org.springframework.stereotype.Service` to `org.apache.dubbo.config.annotation.Service`. Consider using `annotation.path()` instead of `annotation.value()` to match `DubboServiceProcessor`. - Confidence: High - Related existing: none — #5815 (annotation default values), #5943 (method config) are different; this is a wrong-import bug. --- _Identified during the 2026-08-02 deep re-scan; full list in [`docs/scan2-2026-08-02/00-consolidated-critical-high.md`](docs/scan2-2026-08-02/00-consolidated-critical-high.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]
