Hi,
   Agree with willem,"copy and paste" always make troubles.
  

 Regards
yangyong.zheng

 ------------------ ???????? ------------------
  ??????: "willem.jiang"<[email protected]>;
 ????????: 2018??3??26??(??????) ????12:23
 ??????: "dev"<[email protected]>;
 
 ????: Re: Propose adding maven archetypes in Java Chassis

 

Hi bismy,

The sample or the demo could be a start point for the user to know better
of ServiceComb Java Chassis.
And maven archetype is the second step, as we cannot predict the business
logic of the user,  normally we just provide a template for them to work on.
The link that you provided is good start point for us. We can provide maven
archetype base on these examples.
In this way the end user could generate a Java chassis edge service project
template in 5 second. They don't need to modify the example code for half
an hour for their own project.


Willem Jiang

Blog: http://willemjiang.blogspot.com (English)
          http://jnn.iteye.com  (Chinese)
Twitter: willemjiang
Weibo: ????willem

On Mon, Mar 26, 2018 at 11:09 AM, bismy <[email protected]> wrote:

> There is CSE demo and document that demonstrate many parts of ServiceComb
> development. I think ServiceComb should create one too. For users, I think
> generate code is not very important thing. But a sample project and the
> documents about the project can help a lot.
>
>
> https://github.com/huawei-microservice-demo/porter
>
> ------------------ ???????? ------------------
> ??????: "??????"<[email protected]>;
> ????????: 2018??3??26??(??????) ????10:15
> ??????: "dev"<[email protected]>;
>
> ????: Propose adding maven archetypes in Java Chassis
>
>
>
> 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