Hi Zen Lin:
   If user create a blank maven project and want import chassis, he must do 
these steps:
   1. Our chassis support multi provider and transport, also support 
integration with spring boot, he must copy right dependencies into pom, and let 
"java-chassis-dependencies" manage versions.
   2. He must create "microservice.yaml" in resources folder and fill right 
setting, so I think he will copy from samples.
   3. He may copy endpoint implement and replace the operations for faster 
rewrite.
  
   So, I think if we need write long user guide 
(http://servicecomb.incubator.apache.org/users/) to explain how to do,why don't 
we just create one with a "hello world" provider, then Fire.
  
   These archetypes not only for scaffold, they will act as template 
project(module) for more common use.
  
   What's archetypes : 
http://maven.apache.org/guides/introduction/introduction-to-archetypes.html
   Camel archetypes : http://camel.apache.org/camel-maven-archetypes.html
   
  
 Regards
yangyong.zheng
  
  ------------------ ???????? ------------------
  ??????: "Zen Lin"<[email protected]>;
 ????????: 2018??3??26??(??????) ????1:01
 ??????: "dev"<[email protected]>;
 
 ????: Re: Propose adding maven archetypes in Java Chassis

 

@ yangyong.zheng,
I guess  you just want archetypes in order to provide scaffolding for
ServiceComb, can you let us know how others provide there archetypes for
conventional practice to reach a consistent development habit with others?


2018-03-26 10:15 GMT+08:00 ?????? <[email protected]>:

> Hi All:
>    Although we had provide many samples to show how develop a microservice
> using chassis,I think we must provide some maven archetypes in order to
> help users start development quickly,including:
>
>    1.business-service-pojo
>      Archetype for create a common microservice using pojo provider.
>    2.business-service-springmvc
>      Archetype for create a common microservice using springmvc provider.
>    3.business-service-with-spring-boot
>      Archetype for create a common microservice using
> spring-boot-starter-provider.
>    4.edge-service
>      Archetype for create an edge microservice using servicecomb edge-core
> with a general router dispatcher.
>    5.edge-service-with-zuul
>      Archetype for create an edge microservice using spring cloud zuul.
>    6.auth-service
>      Archetype for create an auth microservice with a simple jwt(Json Web
> Token) authentication.
>
>    After we publish these archetypes,uses can generate them by "mvn
> archetype:generate" and modify further.
>
>  Regards
>  yangyong.zheng

Reply via email to