You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicecomb.apache.org by 郑扬勇 <ya...@qq.com> on 2018/03/26 02:15:24 UTC
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
回复： Propose adding maven archetypes in Java Chassis
Posted by bismy <bi...@qq.com>.
Agreed. We can add a brief readme to each generated projects and write some user guides how to use archetypes.
------------------ 原始邮件 ------------------
发件人: "Zen Lin"<ze...@gmail.com>;
发送时间: 2018年3月26日(星期一) 晚上7:12
收件人: "dev"<de...@servicecomb.apache.org>;
主题: Re: Propose adding maven archetypes in Java Chassis
Thanks to yangyong, to my opinion, I quite agree with you, It should be
useful to users and the community, and what about others's opinion?
2018-03-26 15:07 GMT+08:00 郑扬勇 <ya...@qq.com>:
> 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"<ze...@gmail.com>;
> 发送时间: 2018年3月26日(星期一) 中午1:01
> 收件人: "dev"<de...@servicecomb.apache.org>;
>
> 主题: 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 郑扬勇 <ya...@qq.com>:
>
> > 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
>
Re: Propose adding maven archetypes in Java Chassis
Posted by Zen Lin <ze...@gmail.com>.
Thanks to yangyong, to my opinion, I quite agree with you, It should be
useful to users and the community, and what about others's opinion?
2018-03-26 15:07 GMT+08:00 郑扬勇 <ya...@qq.com>:
> 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"<ze...@gmail.com>;
> 发送时间: 2018年3月26日(星期一) 中午1:01
> 收件人: "dev"<de...@servicecomb.apache.org>;
>
> 主题: 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 郑扬勇 <ya...@qq.com>:
>
> > 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
>
Re: Propose adding maven archetypes in Java Chassis
Posted by 郑扬勇 <ya...@qq.com>.
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"<ze...@gmail.com>;
发送时间: 2018年3月26日(星期一) 中午1:01
收件人: "dev"<de...@servicecomb.apache.org>;
主题: 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 郑扬勇 <ya...@qq.com>:
> 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
Re: Propose adding maven archetypes in Java Chassis
Posted by Zen Lin <ze...@gmail.com>.
@ 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 郑扬勇 <ya...@qq.com>:
> 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
Re: Propose adding maven archetypes in Java Chassis
Posted by 郑扬勇 <ya...@qq.com>.
Hi,
Agree with willem,"copy and paste" always make troubles.
Regards
yangyong.zheng
------------------ 原始邮件 ------------------
发件人: "willem.jiang"<wi...@gmail.com>;
发送时间: 2018年3月26日(星期一) 中午12:23
收件人: "dev"<de...@servicecomb.apache.org>;
主题: 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 <bi...@qq.com> 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
>
> ------------------ 原始邮件 ------------------
> 发件人: "郑扬勇"<ya...@qq.com>;
> 发送时间: 2018年3月26日(星期一) 上午10:15
> 收件人: "dev"<de...@servicecomb.apache.org>;
>
> 主题: 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
>
Re: Propose adding maven archetypes in Java Chassis
Posted by Willem Jiang <wi...@gmail.com>.
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 <bi...@qq.com> 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
>
> ------------------ 原始邮件 ------------------
> 发件人: "郑扬勇"<ya...@qq.com>;
> 发送时间: 2018年3月26日(星期一) 上午10:15
> 收件人: "dev"<de...@servicecomb.apache.org>;
>
> 主题: 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
>
回复：Propose adding maven archetypes in Java Chassis
Posted by bismy <bi...@qq.com>.
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
------------------ 原始邮件 ------------------
发件人: "郑扬勇"<ya...@qq.com>;
发送时间: 2018年3月26日(星期一) 上午10:15
收件人: "dev"<de...@servicecomb.apache.org>;
主题: 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