+1 for updating the documents and examples. As we support cse, and servicecomb prefix at the same time, the old configuration can still work (maybe we can add some info log to tell the user we are going to update the configuration setting). It's better to use the servicecomb prefix before releasing Servicecomb 1.0.0.
Any thoughts? Willem Jiang Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On Mon, Apr 23, 2018 at 9:48 AM, 郑扬勇 <[email protected]> wrote: > Hi ,all : > we had support both style of configuration for a long time (since > 0.2.0): https://github.com/apache/incubator-servicecomb-java- > chassis/pull/91 > But all demos and samples in our code still use 'cse.xxx' such as : > > APPLICATION_ID: multiple > service_description: > name: a-server > version: 0.0.1 > cse: > <------- old > service: > registry: > address: http://127.0.0.1:30100 > rest: > address: 0.0.0.0:8080 > highway: > address: 0.0.0.0:7070 > > I think it's time we may change all of them to 'servicecomb.xxx' like : > > APPLICATION_ID: multiple > service_description: > name: a-server > version: 0.0.1 > servicecomb: <------- > new > service: > registry: > address: http://127.0.0.1:30100 > rest: > address: 0.0.0.0:8080 > highway: > address: 0.0.0.0:7070 > > Any other ideas or suggestions are welcome ! > > Yangyong Zheng > Best Regards !
