[Question] <title>升级shenyu admin 2.7版本后,原有的2.5版本客户端如何兼容使用namesapce
- Dominant language
- Java
- Stars
- 8.8k
- Forks
- 3.1k
- Avg merge
- 7d 1h
- Merged PRs (30d)
- 85
Description
### Question
1. 我们之前基于shenyu admin 2.5版本 + shenyu-spring-boot-starter-gateway 2.5版本部署了网关集群,采用nacos 2.3进行数据同步服务。我们后台的服务基于springboot 2.3.1+jdk8, 并采用shenyu-spring-boot-starter-client-springmvc 2.5版本进行了shenyu client注册。
2. 当前我们期望升级至shenyu admin 2.7版本。原有的client服务的注册类型从nacos改为了http(shenyu.register.registerType),.经过试验可以注册,但是只能注册到shenyu admin的默认命名空间(default namespace)上,似乎shenyu-spring-boot-starter-client-springmvc 2.5不能识别shenyu.namespace属性从而指定命名空间。
3. 我们尝试升级shenyu-spring-boot-starter-client-springmvc至2.7版本,但受限于原项目springboot 2.3.1+jdk8未能成功。如果我们升级原项目springboot和jdk版本,则涉及项目较多,工作量很大。请问是否有尽量减少原项目改造进行shenyu admin 升级的办法?
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue describes compatibility between ShenYu Admin 2.5 and 2.7, Spring Boot 2.3.1, JDK 8, and namespace registration, but names no source files or tests. Start by tracing the 2.5 client registration configuration and namespace handling, then define done as a documented upgrade path that avoids unnecessary application-wide upgrades.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring-boot
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100