This is a proposal and not implement yet. I am thinking a better way to solve this problem. Maybe we first print some convention check warning messages and make this change in the near future. I am going to submit a PR to demonstrate that.
------------------ ???????? ------------------ ??????: "willem.jiang"<willem.ji...@gmail.com>; ????????: 2018??4??11??(??????) ????6:02 ??????: "dev"<email@example.com>; ????: Re: [java-chassis and other]About naming conventions for MicroserviceName, Schema Id and Operation Id Hi Liubo, I think it's import to document this kind compatible change in our release note. Please update the release note file, with a new section of break change to highlight this issue and provide suggestion for the user.  https://github.com/apache/incubator-servicecomb-java-chassis/blob/master/etc/releaseNotes.md Willem Jiang Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: ????willem On Tue, Apr 10, 2018 at 5:43 PM, bismy <bi...@qq.com> wrote: > Hi All, > > > Background: > As many features depend on these name and frequently used in yamls, > environment keys, and in program parsing, like in PR: > https://github.com/apache/incubator-servicecomb-java-chassis/pull/577 > > > If name conventions is not defined, this will cause a lot of compatible > issue. > > > e.g. when PR #577 has merged, following code will not work > > > 1. RPC define > @RpcSchema() > class xxx > > > 2. RPC Referent > @RpcReference(microserviceName="xx') > Service s > > > Suggestions: > 1. require Microservice Name, Schema Id and Operation Id to follow the > naming convention: ^[a-zA-Z]+[a-zA-Z]* > 2. validate names when startup. Do not support default schemaId features, > users must specify it implicitly. > 3. Given errors and suggestions(e.g. operation id not valid, use > @ApiOpertion to give explicit id. > > > > > Any suggestions and regards.