Re: avro serialization implement

[Ian Luo]

We don't have. It is a good idea to put it into 'contribution' section on
dubbo website.

On Thu, Jul 12, 2018 at 10:23 AM Huxing Zhang  wrote:

> Hi,
>
> Do we have a documentation/guide about how to help projects go into
> the ecosystem?
>
> On Wed, Jul 11, 2018 at 8:10 PM, Ian Luo  wrote:
> > Tianbao,
> >
> > I've created https://github.com/dubbo/dubbo-serialization-avro, and also
> > invite you into dubbo group. Pls. login github and accept my invitation,
> > then you are ready to go :)
> >
> > Welcome to the community.
> >
> > Thanks,
> > -Ian.
> >
> > On Wed, Jul 11, 2018 at 12:32 PM wu tianbiao  wrote:
> >
> >> OK，I understand.
> >>
> >> Let’s do this.
> >>
> >>
> >>
> >> 发送自 Windows 10 版邮件应用
> >>
> >>
> >>
> >> 
> >> 发件人: Ian Luo 
> >> 发送时间: Wednesday, July 11, 2018 10:09:20 AM
> >> 收件人: dev@dubbo.apache.org
> >> 主题: Re: avro serialization implement
> >>
> >> My GitHub id is beiwei30. Let's do this, I will create one new project
> >> under dubbo group, then invite you into dubbo group so that you could
> >> migrate your code into this new project. What do you think?
> >>
> >> On Tue, Jul 10, 2018 at 6:01 PM wu tianbiao  wrote:
> >>
> >> > Hi Ian Luo,
> >> >
> >> > I’m sorry to say, I can’t operate on GitHub.
> >> >
> >> > And I just invite lan[https://github.com/lan] as collaborator.
> >> >
> >> > Did you mind to show me more detail?
> >> >
> >> > Thx very much!
> >> >
> >> >
> >> >
> >> > 发送自 Windows 10 版邮件应用
> >> >
> >> >
> >> >
> >> > 
> >> > 发件人: Ian Luo 
> >> > 发送时间: Tuesday, July 10, 2018 10:54:49 AM
> >> > 收件人: dev@dubbo.apache.org
> >> > 主题: Re: avro serialization implement
> >> >
> >> > TianBiao,
> >> >
> >> > Would you mind to grant me the ownership of your project so that I
> could
> >> > transfer your project into dubbo eco system [1]?
> >> >
> >> > Thanks,
> >> > -Ian.
> >> >
> >> > 1. http://github.com/dubbo
> >> >
> >> > On Mon, Jul 9, 2018 at 5:56 PM wu tianbiao 
> wrote:
> >> >
> >> > > Hi all,
> >> > >
> >> > > As @diecui1202 mention, now Dubbo
> >> > > recommend place extensions at ecosystem.
> >> > >
> >> > > So I move the RP to an separate project.
> >> > >
> >> > >
> >> > >
> >> > > addressed here:
> >> https://github.com/playaround88/dubbo-serialization-avro
> >> > >
> >> > >
> >> > >
> >> > > Thx all
> >> > >
> >> > >
> >> > >
> >> > > 
> >> > > From: wu tianbiao 
> >> > > Sent: Monday, July 9, 2018 3:52:06 PM
> >> > > To: dev
> >> > > Subject: avro serialization implement
> >> > >
> >> > > Hi all,
> >> > >
> >> > > I post a PR for avro serialization implement. URL:
> >> > > https://github.com/apache/incubator-dubbo/pull/1994
> >> > >
> >> > > As @chickenlj mention, so send an
> mail
> >> > here
> >> > > to discuss whether to remove this extension to the ecos.
> >> > >
> >> > >
> >> > >
> >> > >
> >> > >
> >> >
> >>
>
> --
> Best Regards！
> Huxing
>

Re: avro serialization implement

[Huxing Zhang]

Hi,

Do we have a documentation/guide about how to help projects go into
the ecosystem?

On Wed, Jul 11, 2018 at 8:10 PM, Ian Luo  wrote:
> Tianbao,
>
> I've created https://github.com/dubbo/dubbo-serialization-avro, and also
> invite you into dubbo group. Pls. login github and accept my invitation,
> then you are ready to go :)
>
> Welcome to the community.
>
> Thanks,
> -Ian.
>
> On Wed, Jul 11, 2018 at 12:32 PM wu tianbiao  wrote:
>
>> OK，I understand.
>>
>> Let’s do this.
>>
>>
>>
>> 发送自 Windows 10 版邮件应用
>>
>>
>>
>> 
>> 发件人: Ian Luo 
>> 发送时间: Wednesday, July 11, 2018 10:09:20 AM
>> 收件人: dev@dubbo.apache.org
>> 主题: Re: avro serialization implement
>>
>> My GitHub id is beiwei30. Let's do this, I will create one new project
>> under dubbo group, then invite you into dubbo group so that you could
>> migrate your code into this new project. What do you think?
>>
>> On Tue, Jul 10, 2018 at 6:01 PM wu tianbiao  wrote:
>>
>> > Hi Ian Luo,
>> >
>> > I’m sorry to say, I can’t operate on GitHub.
>> >
>> > And I just invite lan[https://github.com/lan] as collaborator.
>> >
>> > Did you mind to show me more detail?
>> >
>> > Thx very much!
>> >
>> >
>> >
>> > 发送自 Windows 10 版邮件应用
>> >
>> >
>> >
>> > 
>> > 发件人: Ian Luo 
>> > 发送时间: Tuesday, July 10, 2018 10:54:49 AM
>> > 收件人: dev@dubbo.apache.org
>> > 主题: Re: avro serialization implement
>> >
>> > TianBiao,
>> >
>> > Would you mind to grant me the ownership of your project so that I could
>> > transfer your project into dubbo eco system [1]?
>> >
>> > Thanks,
>> > -Ian.
>> >
>> > 1. http://github.com/dubbo
>> >
>> > On Mon, Jul 9, 2018 at 5:56 PM wu tianbiao  wrote:
>> >
>> > > Hi all,
>> > >
>> > > As @diecui1202 mention, now Dubbo
>> > > recommend place extensions at ecosystem.
>> > >
>> > > So I move the RP to an separate project.
>> > >
>> > >
>> > >
>> > > addressed here:
>> https://github.com/playaround88/dubbo-serialization-avro
>> > >
>> > >
>> > >
>> > > Thx all
>> > >
>> > >
>> > >
>> > > 
>> > > From: wu tianbiao 
>> > > Sent: Monday, July 9, 2018 3:52:06 PM
>> > > To: dev
>> > > Subject: avro serialization implement
>> > >
>> > > Hi all,
>> > >
>> > > I post a PR for avro serialization implement. URL:
>> > > https://github.com/apache/incubator-dubbo/pull/1994
>> > >
>> > > As @chickenlj mention, so send an mail
>> > here
>> > > to discuss whether to remove this extension to the ecos.
>> > >
>> > >
>> > >
>> > >
>> > >
>> >
>>

-- 
Best Regards！
Huxing

答复: avro serialization implement

[wu tianbiao]

Hi,

It’s used ‘org.apache’ before, and just changed for transfer, When I move the 
project separate, dependency cannot download. So I just ref 
Dubbo-serialization-native-thrift’s pom.xml.

I will do this tonight, and I planed to complete the REDME.



THX and good luck!



发送自 Windows 10 版邮件应用




发件人: Ian Luo 
发送时间: Thursday, July 12, 2018 1:09:52 PM
收件人: dev@dubbo.apache.org
主题: Re: avro serialization implement

Tianbiao,

I take a look at the project, would you mind to change pom.xml to depend on
Dubbo's latest version, which should have package name 'org.apache' instead
of 'com.alibaba'?

Pls. also update README.md too, to include at least a quick start for avro
use.

Thanks,
-Ian.


On Thu, Jul 12, 2018 at 10:55 AM wu tianbiao  wrote:

> Hi all,
>
> I have transfer Dubbo-serialize-avro to Dubbo ecosystem.
>
> Huxing’s suggestion is good idea. When I do this, I feel some confused. We
> should add a guild about this work.
>
> 1. Pull request template should add well-marked description of Dubbo
> ecosystem.
>
> 2. Dubbo home page, Developer guild, and so on should make some change.
>
> 3. Good extension project template.
>
> 4. When I do transfer, Dubbo dependency should change to group to
> Alibaba.
>
>
>
>
>
> 
> 发件人: Huxing Zhang 
> 发送时间: Thursday, July 12, 2018 10:22:33 AM
> 收件人: dev@dubbo.apache.org
> 主题: Re: avro serialization implement
>
> Hi,
>
> Do we have a documentation/guide about how to help projects go into
> the ecosystem?
>
> On Wed, Jul 11, 2018 at 8:10 PM, Ian Luo  wrote:
> > Tianbao,
> >
> > I've created https://github.com/dubbo/dubbo-serialization-avro, and also
> > invite you into dubbo group. Pls. login github and accept my invitation,
> > then you are ready to go :)
> >
> > Welcome to the community.
> >
> > Thanks,
> > -Ian.
> >
> > On Wed, Jul 11, 2018 at 12:32 PM wu tianbiao  wrote:
> >
> >> OK，I understand.
> >>
> >> Let’s do this.
> >>
> >>
> >>
> >> 发送自 Windows 10 版邮件应用
> >>
> >>
> >>
> >> 
> >> 发件人: Ian Luo 
> >> 发送时间: Wednesday, July 11, 2018 10:09:20 AM
> >> 收件人: dev@dubbo.apache.org
> >> 主题: Re: avro serialization implement
> >>
> >> My GitHub id is beiwei30. Let's do this, I will create one new project
> >> under dubbo group, then invite you into dubbo group so that you could
> >> migrate your code into this new project. What do you think?
> >>
> >> On Tue, Jul 10, 2018 at 6:01 PM wu tianbiao  wrote:
> >>
> >> > Hi Ian Luo,
> >> >
> >> > I’m sorry to say, I can’t operate on GitHub.
> >> >
> >> > And I just invite lan[https://github.com/lan] as collaborator.
> >> >
> >> > Did you mind to show me more detail?
> >> >
> >> > Thx very much!
> >> >
> >> >
> >> >
> >> > 发送自 Windows 10 版邮件应用
> >> >
> >> >
> >> >
> >> > 
> >> > 发件人: Ian Luo 
> >> > 发送时间: Tuesday, July 10, 2018 10:54:49 AM
> >> > 收件人: dev@dubbo.apache.org
> >> > 主题: Re: avro serialization implement
> >> >
> >> > TianBiao,
> >> >
> >> > Would you mind to grant me the ownership of your project so that I
> could
> >> > transfer your project into dubbo eco system [1]?
> >> >
> >> > Thanks,
> >> > -Ian.
> >> >
> >> > 1. http://github.com/dubbo
> >> >
> >> > On Mon, Jul 9, 2018 at 5:56 PM wu tianbiao 
> wrote:
> >> >
> >> > > Hi all,
> >> > >
> >> > > As @diecui1202 mention, now Dubbo
> >> > > recommend place extensions at ecosystem.
> >> > >
> >> > > So I move the RP to an separate project.
> >> > >
> >> > >
> >> > >
> >> > > addressed here:
> >> https://github.com/playaround88/dubbo-serialization-avro
> >> > >
> >> > >
> >> > >
> >> > > Thx all
> >> > >
> >> > >
> >> > >
> >> > > 
> >> > > From: wu tianbiao 
> >> > > Sent: Monday, July 9, 2018 3:52:06 PM
> >> > > To: dev
> >> > > Subject: avro serialization implement
> >> > >
> >> > > Hi all,
> >> > >
> >> > > I post a PR for avro serialization implement. URL:
> >> > > https://github.com/apache/incubator-dubbo/pull/1994
> >> > >
> >> > > As @chickenlj mention, so send an
> mail
> >> > here
> >> > > to discuss whether to remove this extension to the ecos.
> >> > >
> >> > >
> >> > >
> >> > >
> >> > >
> >> >
> >>
>
> --
> Best Regards！
> Huxing
>

Re: 答复: avro serialization implement

[Huxing Zhang]

Hi,

Great suggestion! Since you have experienced, would you mind draft a
document about this process?

On Thu, Jul 12, 2018 at 10:54 AM, wu tianbiao  wrote:
> Hi all,
>
> I have transfer Dubbo-serialize-avro to Dubbo ecosystem.
>
> Huxing’s suggestion is good idea. When I do this, I feel some confused. We 
> should add a guild about this work.
>
> 1. Pull request template should add well-marked description of Dubbo 
> ecosystem.
>
> 2. Dubbo home page, Developer guild, and so on should make some change.
>
> 3. Good extension project template.
>
> 4. When I do transfer, Dubbo dependency should change to group to Alibaba.
>
>
>
>
>
> 
> 发件人: Huxing Zhang 
> 发送时间: Thursday, July 12, 2018 10:22:33 AM
> 收件人: dev@dubbo.apache.org
> 主题: Re: avro serialization implement
>
> Hi,
>
> Do we have a documentation/guide about how to help projects go into
> the ecosystem?
>
> On Wed, Jul 11, 2018 at 8:10 PM, Ian Luo  wrote:
>> Tianbao,
>>
>> I've created https://github.com/dubbo/dubbo-serialization-avro, and also
>> invite you into dubbo group. Pls. login github and accept my invitation,
>> then you are ready to go :)
>>
>> Welcome to the community.
>>
>> Thanks,
>> -Ian.
>>
>> On Wed, Jul 11, 2018 at 12:32 PM wu tianbiao  wrote:
>>
>>> OK，I understand.
>>>
>>> Let’s do this.
>>>
>>>
>>>
>>> 发送自 Windows 10 版邮件应用
>>>
>>>
>>>
>>> 
>>> 发件人: Ian Luo 
>>> 发送时间: Wednesday, July 11, 2018 10:09:20 AM
>>> 收件人: dev@dubbo.apache.org
>>> 主题: Re: avro serialization implement
>>>
>>> My GitHub id is beiwei30. Let's do this, I will create one new project
>>> under dubbo group, then invite you into dubbo group so that you could
>>> migrate your code into this new project. What do you think?
>>>
>>> On Tue, Jul 10, 2018 at 6:01 PM wu tianbiao  wrote:
>>>
>>> > Hi Ian Luo,
>>> >
>>> > I’m sorry to say, I can’t operate on GitHub.
>>> >
>>> > And I just invite lan[https://github.com/lan] as collaborator.
>>> >
>>> > Did you mind to show me more detail?
>>> >
>>> > Thx very much!
>>> >
>>> >
>>> >
>>> > 发送自 Windows 10 版邮件应用
>>> >
>>> >
>>> >
>>> > 
>>> > 发件人: Ian Luo 
>>> > 发送时间: Tuesday, July 10, 2018 10:54:49 AM
>>> > 收件人: dev@dubbo.apache.org
>>> > 主题: Re: avro serialization implement
>>> >
>>> > TianBiao,
>>> >
>>> > Would you mind to grant me the ownership of your project so that I could
>>> > transfer your project into dubbo eco system [1]?
>>> >
>>> > Thanks,
>>> > -Ian.
>>> >
>>> > 1. http://github.com/dubbo
>>> >
>>> > On Mon, Jul 9, 2018 at 5:56 PM wu tianbiao  wrote:
>>> >
>>> > > Hi all,
>>> > >
>>> > > As @diecui1202 mention, now Dubbo
>>> > > recommend place extensions at ecosystem.
>>> > >
>>> > > So I move the RP to an separate project.
>>> > >
>>> > >
>>> > >
>>> > > addressed here:
>>> https://github.com/playaround88/dubbo-serialization-avro
>>> > >
>>> > >
>>> > >
>>> > > Thx all
>>> > >
>>> > >
>>> > >
>>> > > 
>>> > > From: wu tianbiao 
>>> > > Sent: Monday, July 9, 2018 3:52:06 PM
>>> > > To: dev
>>> > > Subject: avro serialization implement
>>> > >
>>> > > Hi all,
>>> > >
>>> > > I post a PR for avro serialization implement. URL:
>>> > > https://github.com/apache/incubator-dubbo/pull/1994
>>> > >
>>> > > As @chickenlj mention, so send an mail
>>> > here
>>> > > to discuss whether to remove this extension to the ecos.
>>> > >
>>> > >
>>> > >
>>> > >
>>> > >
>>> >
>>>
>
> --
> Best Regards！
> Huxing



-- 
Best Regards！
Huxing

答复: 答复: avro serialization implement

[wu tianbiao]

Ok, I’m be happy to do.

I plan complete before Sunday, so we can discuss at weekend, and make some 
improve.



Good luck!




发件人: Huxing Zhang 
发送时间: Thursday, July 12, 2018 1:36:42 PM
收件人: dev@dubbo.apache.org
主题: Re: 答复: avro serialization implement

Hi,

Great suggestion! Since you have experienced, would you mind draft a
document about this process?

On Thu, Jul 12, 2018 at 10:54 AM, wu tianbiao  wrote:
> Hi all,
>
> I have transfer Dubbo-serialize-avro to Dubbo ecosystem.
>
> Huxing’s suggestion is good idea. When I do this, I feel some confused. We 
> should add a guild about this work.
>
> 1. Pull request template should add well-marked description of Dubbo 
> ecosystem.
>
> 2. Dubbo home page, Developer guild, and so on should make some change.
>
> 3. Good extension project template.
>
> 4. When I do transfer, Dubbo dependency should change to group to Alibaba.
>
>
>
>
>
> 
> 发件人: Huxing Zhang 
> 发送时间: Thursday, July 12, 2018 10:22:33 AM
> 收件人: dev@dubbo.apache.org
> 主题: Re: avro serialization implement
>
> Hi,
>
> Do we have a documentation/guide about how to help projects go into
> the ecosystem?
>
> On Wed, Jul 11, 2018 at 8:10 PM, Ian Luo  wrote:
>> Tianbao,
>>
>> I've created https://github.com/dubbo/dubbo-serialization-avro, and also
>> invite you into dubbo group. Pls. login github and accept my invitation,
>> then you are ready to go :)
>>
>> Welcome to the community.
>>
>> Thanks,
>> -Ian.
>>
>> On Wed, Jul 11, 2018 at 12:32 PM wu tianbiao  wrote:
>>
>>> OK，I understand.
>>>
>>> Let’s do this.
>>>
>>>
>>>
>>> 发送自 Windows 10 版邮件应用
>>>
>>>
>>>
>>> 
>>> 发件人: Ian Luo 
>>> 发送时间: Wednesday, July 11, 2018 10:09:20 AM
>>> 收件人: dev@dubbo.apache.org
>>> 主题: Re: avro serialization implement
>>>
>>> My GitHub id is beiwei30. Let's do this, I will create one new project
>>> under dubbo group, then invite you into dubbo group so that you could
>>> migrate your code into this new project. What do you think?
>>>
>>> On Tue, Jul 10, 2018 at 6:01 PM wu tianbiao  wrote:
>>>
>>> > Hi Ian Luo,
>>> >
>>> > I’m sorry to say, I can’t operate on GitHub.
>>> >
>>> > And I just invite lan[https://github.com/lan] as collaborator.
>>> >
>>> > Did you mind to show me more detail?
>>> >
>>> > Thx very much!
>>> >
>>> >
>>> >
>>> > 发送自 Windows 10 版邮件应用
>>> >
>>> >
>>> >
>>> > 
>>> > 发件人: Ian Luo 
>>> > 发送时间: Tuesday, July 10, 2018 10:54:49 AM
>>> > 收件人: dev@dubbo.apache.org
>>> > 主题: Re: avro serialization implement
>>> >
>>> > TianBiao,
>>> >
>>> > Would you mind to grant me the ownership of your project so that I could
>>> > transfer your project into dubbo eco system [1]?
>>> >
>>> > Thanks,
>>> > -Ian.
>>> >
>>> > 1. http://github.com/dubbo
>>> >
>>> > On Mon, Jul 9, 2018 at 5:56 PM wu tianbiao  wrote:
>>> >
>>> > > Hi all,
>>> > >
>>> > > As @diecui1202 mention, now Dubbo
>>> > > recommend place extensions at ecosystem.
>>> > >
>>> > > So I move the RP to an separate project.
>>> > >
>>> > >
>>> > >
>>> > > addressed here:
>>> https://github.com/playaround88/dubbo-serialization-avro
>>> > >
>>> > >
>>> > >
>>> > > Thx all
>>> > >
>>> > >
>>> > >
>>> > > 
>>> > > From: wu tianbiao 
>>> > > Sent: Monday, July 9, 2018 3:52:06 PM
>>> > > To: dev
>>> > > Subject: avro serialization implement
>>> > >
>>> > > Hi all,
>>> > >
>>> > > I post a PR for avro serialization implement. URL:
>>> > > https://github.com/apache/incubator-dubbo/pull/1994
>>> > >
>>> > > As @chickenlj mention, so send an mail
>>> > here
>>> > > to discuss whether to remove this extension to the ecos.
>>> > >
>>> > >
>>> > >
>>> > >
>>> > >
>>> >
>>>
>
> --
> Best Regards！
> Huxing



--
Best Regards！
Huxing

答复: avro serialization implement

[wu tianbiao]

Hi all,

I have transfer Dubbo-serialize-avro to Dubbo ecosystem.

Huxing’s suggestion is good idea. When I do this, I feel some confused. We 
should add a guild about this work.

1. Pull request template should add well-marked description of Dubbo 
ecosystem.

2. Dubbo home page, Developer guild, and so on should make some change.

3. Good extension project template.

4. When I do transfer, Dubbo dependency should change to group to Alibaba.






发件人: Huxing Zhang 
发送时间: Thursday, July 12, 2018 10:22:33 AM
收件人: dev@dubbo.apache.org
主题: Re: avro serialization implement

Hi,

Do we have a documentation/guide about how to help projects go into
the ecosystem?

On Wed, Jul 11, 2018 at 8:10 PM, Ian Luo  wrote:
> Tianbao,
>
> I've created https://github.com/dubbo/dubbo-serialization-avro, and also
> invite you into dubbo group. Pls. login github and accept my invitation,
> then you are ready to go :)
>
> Welcome to the community.
>
> Thanks,
> -Ian.
>
> On Wed, Jul 11, 2018 at 12:32 PM wu tianbiao  wrote:
>
>> OK，I understand.
>>
>> Let’s do this.
>>
>>
>>
>> 发送自 Windows 10 版邮件应用
>>
>>
>>
>> 
>> 发件人: Ian Luo 
>> 发送时间: Wednesday, July 11, 2018 10:09:20 AM
>> 收件人: dev@dubbo.apache.org
>> 主题: Re: avro serialization implement
>>
>> My GitHub id is beiwei30. Let's do this, I will create one new project
>> under dubbo group, then invite you into dubbo group so that you could
>> migrate your code into this new project. What do you think?
>>
>> On Tue, Jul 10, 2018 at 6:01 PM wu tianbiao  wrote:
>>
>> > Hi Ian Luo,
>> >
>> > I’m sorry to say, I can’t operate on GitHub.
>> >
>> > And I just invite lan[https://github.com/lan] as collaborator.
>> >
>> > Did you mind to show me more detail?
>> >
>> > Thx very much!
>> >
>> >
>> >
>> > 发送自 Windows 10 版邮件应用
>> >
>> >
>> >
>> > 
>> > 发件人: Ian Luo 
>> > 发送时间: Tuesday, July 10, 2018 10:54:49 AM
>> > 收件人: dev@dubbo.apache.org
>> > 主题: Re: avro serialization implement
>> >
>> > TianBiao,
>> >
>> > Would you mind to grant me the ownership of your project so that I could
>> > transfer your project into dubbo eco system [1]?
>> >
>> > Thanks,
>> > -Ian.
>> >
>> > 1. http://github.com/dubbo
>> >
>> > On Mon, Jul 9, 2018 at 5:56 PM wu tianbiao  wrote:
>> >
>> > > Hi all,
>> > >
>> > > As @diecui1202 mention, now Dubbo
>> > > recommend place extensions at ecosystem.
>> > >
>> > > So I move the RP to an separate project.
>> > >
>> > >
>> > >
>> > > addressed here:
>> https://github.com/playaround88/dubbo-serialization-avro
>> > >
>> > >
>> > >
>> > > Thx all
>> > >
>> > >
>> > >
>> > > 
>> > > From: wu tianbiao 
>> > > Sent: Monday, July 9, 2018 3:52:06 PM
>> > > To: dev
>> > > Subject: avro serialization implement
>> > >
>> > > Hi all,
>> > >
>> > > I post a PR for avro serialization implement. URL:
>> > > https://github.com/apache/incubator-dubbo/pull/1994
>> > >
>> > > As @chickenlj mention, so send an mail
>> > here
>> > > to discuss whether to remove this extension to the ecos.
>> > >
>> > >
>> > >
>> > >
>> > >
>> >
>>

--
Best Regards！
Huxing

Re: 答复: avro serialization implement

[Yong Zhu]

That's great.

On Thu, Jul 12, 2018 at 1:49 PM wu tianbiao  wrote:

> Ok, I’m be happy to do.
>
> I plan complete before Sunday, so we can discuss at weekend, and make some
> improve.
>
>
>
> Good luck!
>
>
>
> 
> 发件人: Huxing Zhang 
> 发送时间: Thursday, July 12, 2018 1:36:42 PM
> 收件人: dev@dubbo.apache.org
> 主题: Re: 答复: avro serialization implement
>
> Hi,
>
> Great suggestion! Since you have experienced, would you mind draft a
> document about this process?
>
> On Thu, Jul 12, 2018 at 10:54 AM, wu tianbiao  wrote:
> > Hi all,
> >
> > I have transfer Dubbo-serialize-avro to Dubbo ecosystem.
> >
> > Huxing’s suggestion is good idea. When I do this, I feel some confused.
> We should add a guild about this work.
> >
> > 1. Pull request template should add well-marked description of Dubbo
> ecosystem.
> >
> > 2. Dubbo home page, Developer guild, and so on should make some
> change.
> >
> > 3. Good extension project template.
> >
> > 4. When I do transfer, Dubbo dependency should change to group to
> Alibaba.
> >
> >
> >
> >
> >
> > 
> > 发件人: Huxing Zhang 
> > 发送时间: Thursday, July 12, 2018 10:22:33 AM
> > 收件人: dev@dubbo.apache.org
> > 主题: Re: avro serialization implement
> >
> > Hi,
> >
> > Do we have a documentation/guide about how to help projects go into
> > the ecosystem?
> >
> > On Wed, Jul 11, 2018 at 8:10 PM, Ian Luo  wrote:
> >> Tianbao,
> >>
> >> I've created https://github.com/dubbo/dubbo-serialization-avro, and
> also
> >> invite you into dubbo group. Pls. login github and accept my invitation,
> >> then you are ready to go :)
> >>
> >> Welcome to the community.
> >>
> >> Thanks,
> >> -Ian.
> >>
> >> On Wed, Jul 11, 2018 at 12:32 PM wu tianbiao 
> wrote:
> >>
> >>> OK，I understand.
> >>>
> >>> Let’s do this.
> >>>
> >>>
> >>>
> >>> 发送自 Windows 10 版邮件应用
> >>>
> >>>
> >>>
> >>> 
> >>> 发件人: Ian Luo 
> >>> 发送时间: Wednesday, July 11, 2018 10:09:20 AM
> >>> 收件人: dev@dubbo.apache.org
> >>> 主题: Re: avro serialization implement
> >>>
> >>> My GitHub id is beiwei30. Let's do this, I will create one new project
> >>> under dubbo group, then invite you into dubbo group so that you could
> >>> migrate your code into this new project. What do you think?
> >>>
> >>> On Tue, Jul 10, 2018 at 6:01 PM wu tianbiao 
> wrote:
> >>>
> >>> > Hi Ian Luo,
> >>> >
> >>> > I’m sorry to say, I can’t operate on GitHub.
> >>> >
> >>> > And I just invite lan[https://github.com/lan] as collaborator.
> >>> >
> >>> > Did you mind to show me more detail?
> >>> >
> >>> > Thx very much!
> >>> >
> >>> >
> >>> >
> >>> > 发送自 Windows 10 版邮件应用
> >>> >
> >>> >
> >>> >
> >>> > 
> >>> > 发件人: Ian Luo 
> >>> > 发送时间: Tuesday, July 10, 2018 10:54:49 AM
> >>> > 收件人: dev@dubbo.apache.org
> >>> > 主题: Re: avro serialization implement
> >>> >
> >>> > TianBiao,
> >>> >
> >>> > Would you mind to grant me the ownership of your project so that I
> could
> >>> > transfer your project into dubbo eco system [1]?
> >>> >
> >>> > Thanks,
> >>> > -Ian.
> >>> >
> >>> > 1. http://github.com/dubbo
> >>> >
> >>> > On Mon, Jul 9, 2018 at 5:56 PM wu tianbiao 
> wrote:
> >>> >
> >>> > > Hi all,
> >>> > >
> >>> > > As @diecui1202 mention, now Dubbo
> >>> > > recommend place extensions at ecosystem.
> >>> > >
> >>> > > So I move the RP to an separate project.
> >>> > >
> >>> > >
> >>> > >
> >>> > > addressed here:
> >>> https://github.com/playaround88/dubbo-serialization-avro
> >>> > >
> >>> > >
> >>> > >
> >>> > > Thx all
> >>> > >
> >>> > >
> >>> > >
> >>> > > 
> >>> > > From: wu tianbiao 
> >>> > > Sent: Monday, July 9, 2018 3:52:06 PM
> >>> > > To: dev
> >>> > > Subject: avro serialization implement
> >>> > >
> >>> > > Hi all,
> >>> > >
> >>> > > I post a PR for avro serialization implement. URL:
> >>> > > https://github.com/apache/incubator-dubbo/pull/1994
> >>> > >
> >>> > > As @chickenlj mention, so send an
> mail
> >>> > here
> >>> > > to discuss whether to remove this extension to the ecos.
> >>> > >
> >>> > >
> >>> > >
> >>> > >
> >>> > >
> >>> >
> >>>
> >
> > --
> > Best Regards！
> > Huxing
>
>
>
> --
> Best Regards！
> Huxing
>

Re: Proposal for Dubbo 3.0

[Minxuan Zhuang]

Hi
Thank you for being interested in Dubbo monitor, If you unregister a a
consumer, the monitor will get the information Immediately,
you can try this by the steps below:
1. start a zookeeper
2 start Dubbo monitor by running MonitorStarter.java
3. download dubbo samples here  and
run dubbo-samples-monitor module
If you start both BasicProvider and BasicConsumer, you can see provider and
consumer info on dubbo monitor, once you stop BasicConsumer, this consumer
info will disappear. the monitor can detect the change by NotifyListener
and this mechanism is very efficient for me, do you have any
suggestion for implementing
this?

On Wed, Jul 11, 2018 at 5:29 PM Andrea Del Bene 
wrote:

> Hi,
>
> I'm very new to Dubbo but I'd like to share some ideas. I am playing around
> trying to implement a simple monitor for Dubbo (this one
> https://github.com/bitstorm/wicket-coreui). To start grasping what I have
> to do I've looked at what dubbo-monitor-simple (
> https://github.com/apache/incubator-dubbo-ops) already does. While the
> overall mechanism is quite clear I find difficult working with the current
> URL-based notification mechanism (I'm referring to interface
> NotifyListener). Extracting informations from url is not trivial and I
> think we might use a more complex and clear object for this task. In
> particular is difficult to be notified if a consumer application has been
> unregistered.
>
> Hope this could be helpful for future improvements.
>
> Thank you.
>
> On Mon, Jul 9, 2018 at 9:32 AM, Liujie Qin  wrote:
>
> >   Hi All, Dubbo has become a excellent RPC framework with the efforts of
> > various partners in the community. However, in the process of
> development,
> > we found some shortcomings of Dubbo 2.x, which is listed as follows:
> >
> >- The maintainability is relatively poor. The code uses a lot of
> >dynamically generated classes. It is difficult to understand and
> > difficult
> >to debug. The code hierarchy is not clear enough, and the calling
> logic
> > is
> >confusing. As an experienced Dubbo developer, sometimes it is
> difficult
> > for
> >me to sort out the calling process of Dubbo 2.x; the more developed,
> the
> >more difficult it is to maintain, so it needs to be refactored in
> order
> > to
> >develop better.
> >- Some extensions cannot meet current needs, such as service addresses
> >push monitoring, performing Filter early interception requests before
> >service addresses selection, printing the process of route selection,
> > etc.
> >- The underlying Dubbo 2.X is based on synchronous calls. The
> >asynchronous call is wrapped synchronously. This introduces
> inaccuracies
> >such as RT during asynchronous calls.
> >- At present, the service metadata information and the address of the
> >Dubbo service are coupled together. Most of the metadata is the same,
> > and
> >the metadata is redundant. At the same time, as the size of the
> machine
> >increases, the Registry is under great pressure, especially when
> machine
> >restart.
> >- The service registry and the configuration center are coupled
> >together, and after splitting, the management and storage of service
> >governance rule data such as routing rules can be better handled.
> >- The core is written based on JDK 1.6 and cannot use the newer JDK
> >features. It is recommended to upgrade JDK to 1.8 and above.
> >
> > For the above reasons, in order to better develop Dubbo and attract more
> > people to participate in the development of the Dubbo community, I
> propose
> > to refactor the Dubbo 2.x code. The newly developed version number is
> Dubbo
> > 3.x. Refactoring Dubbo 3.x will have the following advantages:
> >
> >- Refactoring core modules to make the code more concise and
> >understandable
> >- Refactoring the routing process, Making the route process to
> Pipeline
> >style,Making the route process can be observed
> >- Add new extension points to make it easier for developers to extend
> >the framework
> >- Add the Service Domain Model to enable developers to handle its
> >lifecycle
> >- Supports asynchronous interface, unified call process returns
> >CompleteFuture, synchronous call process uses CompleteFuture wrapper;
> > Solve
> >the problem of inaccurate statistics such as RT during asynchronous
> call
> >- Splitting out the Configuration Center and Registry for better
> control
> >and support for larger clusters
> >- Prepare for new features such as Http2 stream、Reactive stream
> >- Performance improvement
> >- And so on
> >
> > Of course, refactoring Dubbo 3.x also faces the following challenges:
> >
> >- A wide range of refactorings that can cause extension points to be
> >incompatible
> >- The Dubbo team may need to maintain two branches at the same time
> for
> >a longer period of time
> >
> > 

Re: 20k Github stars for Dubbo

[Xin Wang]

Awesome

Zhanhui Li  于2018年7月9日周一 下午2:52写道：

> Congratulations!
>
> > 在 2018年7月9日，下午2:42，Mercy  写道：
> >
> > Great Job!
> >
> >
> > Kind regards,
> >
> > Mercy
> >
> >
> > 在 2018/7/9 上午11:51, Huxing Zhang 写道:
> >> Hi All,
> >>
> >> I am happy to announce that Dubbo has reached 20k Github stars
> >> today[1], an important milestone for Dubbo.
> >>
> >> Dubbo is the first Java project that reaches 20k Github stars[2] in
> >> Apache Software Foundation, the second most[3] in terms of all
> >> languages in the foundation.
> >>
> >> Dubbo is open sources in 2012, till now, it is the most popular RPC
> >> framework in China, and has been adopted by many companies for their
> >> production system, including:
> >>
> >> Internet companies:
> >> * Alibaba
> >> * Dangdang
> >> * Qunar
> >> * Netease
> >> * etc.
> >>
> >> State-owned enterprises:
> >> * Industrial and Commercial Bank of China
> >> * China Telecom
> >> * China Life
> >> * etc.
> >>
> >> More use case can be found at the homepage:
> http://dubbo.incubator.apache.org/
> >>
> >> As an incubator project, the Dubbo PPMC will continue to make the
> >> community open and diverse, and we are more than happy to have
> >> everyone come to contribute, any question can be discussed on dev
> >> mailing list.
> >>
> >> [1] https://github.com/apache/incubator-dubbo
> >> [2]
> https://github.com/search?l=Java=desc=org%3Aapache=stars=Repositories
> >> [3]
> https://github.com/search?o=desc=org%3Aapache=stars=Repositories
> >>
> >
> >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

RE: avro serialization implement

[wu tianbiao]

Hi all,

As @diecui1202 mention, now Dubbo recommend 
place extensions at ecosystem.

So I move the RP to an separate project.



addressed here: https://github.com/playaround88/dubbo-serialization-avro



Thx all




From: wu tianbiao 
Sent: Monday, July 9, 2018 3:52:06 PM
To: dev
Subject: avro serialization implement

Hi all,

I post a PR for avro serialization implement. URL: 
https://github.com/apache/incubator-dubbo/pull/1994

As @chickenlj mention, so send an mail here to 
discuss whether to remove this extension to the ecos.

Re: avro serialization implement

[Yong Zhu]

Great, welcome to contribute

On Mon, Jul 9, 2018 at 5:56 PM wu tianbiao  wrote:

> Hi all,
>
> As @diecui1202 mention, now Dubbo
> recommend place extensions at ecosystem.
>
> So I move the RP to an separate project.
>
>
>
> addressed here: https://github.com/playaround88/dubbo-serialization-avro
>
>
>
> Thx all
>
>
>
> 
> From: wu tianbiao 
> Sent: Monday, July 9, 2018 3:52:06 PM
> To: dev
> Subject: avro serialization implement
>
> Hi all,
>
> I post a PR for avro serialization implement. URL:
> https://github.com/apache/incubator-dubbo/pull/1994
>
> As @chickenlj mention, so send an mail here
> to discuss whether to remove this extension to the ecos.
>
>
>
>
>

Re: 20k Github stars for Dubbo

[Yong Zhu]

What a new stage! Congratulations!
On Mon, Jul 9, 2018 at 3:34 PM Shalitha Suranga 
wrote:

> Awesome!! congrats
>
> On Mon, Jul 9, 2018 at 12:39 PM Prateek Chanda 
> wrote:
>
> > Congratulations!!  Maybe I can contribute to it when I get free time.
> >
> > Prateek
> >
> >
> >
> > On 9 July 2018 at 12:15, Zhanhui Li  wrote:
> >
> > > Congratulations!
> > >
> > > > 在 2018年7月9日，下午2:42，Mercy  写道：
> > > >
> > > > Great Job!
> > > >
> > > >
> > > > Kind regards,
> > > >
> > > > Mercy
> > > >
> > > >
> > > > 在 2018/7/9 上午11:51, Huxing Zhang 写道:
> > > >> Hi All,
> > > >>
> > > >> I am happy to announce that Dubbo has reached 20k Github stars
> > > >> today[1], an important milestone for Dubbo.
> > > >>
> > > >> Dubbo is the first Java project that reaches 20k Github stars[2] in
> > > >> Apache Software Foundation, the second most[3] in terms of all
> > > >> languages in the foundation.
> > > >>
> > > >> Dubbo is open sources in 2012, till now, it is the most popular RPC
> > > >> framework in China, and has been adopted by many companies for their
> > > >> production system, including:
> > > >>
> > > >> Internet companies:
> > > >> * Alibaba
> > > >> * Dangdang
> > > >> * Qunar
> > > >> * Netease
> > > >> * etc.
> > > >>
> > > >> State-owned enterprises:
> > > >> * Industrial and Commercial Bank of China
> > > >> * China Telecom
> > > >> * China Life
> > > >> * etc.
> > > >>
> > > >> More use case can be found at the homepage:
> > > http://dubbo.incubator.apache.org/
> > > >>
> > > >> As an incubator project, the Dubbo PPMC will continue to make the
> > > >> community open and diverse, and we are more than happy to have
> > > >> everyone come to contribute, any question can be discussed on dev
> > > >> mailing list.
> > > >>
> > > >> [1] https://github.com/apache/incubator-dubbo
> > > >> [2] https://github.com/search?l=Java=desc=org%3Aapache=
> > > stars=Repositories
> > > >> [3] https://github.com/search?o=desc=org%3Aapache=stars;
> > > type=Repositories
> > > >>
> > > >
> > > >
> > > >
> > > > -
> > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> > >
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > > For additional commands, e-mail: dev-h...@community.apache.org
> > >
> > >
> >
>
>
> --
> Regards,
>
> *Shalitha Suranga Bsc. CS (UG)*
> www.shalithasuranga.me
>

Re: 20k Github stars for Dubbo

[Prateek Chanda]

Congratulations!!  Maybe I can contribute to it when I get free time.

Prateek



On 9 July 2018 at 12:15, Zhanhui Li  wrote:

> Congratulations!
>
> > 在 2018年7月9日，下午2:42，Mercy  写道：
> >
> > Great Job!
> >
> >
> > Kind regards,
> >
> > Mercy
> >
> >
> > 在 2018/7/9 上午11:51, Huxing Zhang 写道:
> >> Hi All,
> >>
> >> I am happy to announce that Dubbo has reached 20k Github stars
> >> today[1], an important milestone for Dubbo.
> >>
> >> Dubbo is the first Java project that reaches 20k Github stars[2] in
> >> Apache Software Foundation, the second most[3] in terms of all
> >> languages in the foundation.
> >>
> >> Dubbo is open sources in 2012, till now, it is the most popular RPC
> >> framework in China, and has been adopted by many companies for their
> >> production system, including:
> >>
> >> Internet companies:
> >> * Alibaba
> >> * Dangdang
> >> * Qunar
> >> * Netease
> >> * etc.
> >>
> >> State-owned enterprises:
> >> * Industrial and Commercial Bank of China
> >> * China Telecom
> >> * China Life
> >> * etc.
> >>
> >> More use case can be found at the homepage:
> http://dubbo.incubator.apache.org/
> >>
> >> As an incubator project, the Dubbo PPMC will continue to make the
> >> community open and diverse, and we are more than happy to have
> >> everyone come to contribute, any question can be discussed on dev
> >> mailing list.
> >>
> >> [1] https://github.com/apache/incubator-dubbo
> >> [2] https://github.com/search?l=Java=desc=org%3Aapache=
> stars=Repositories
> >> [3] https://github.com/search?o=desc=org%3Aapache=stars;
> type=Repositories
> >>
> >
> >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>
>

Re: 20k Github stars for Dubbo

[xingxuechao]

Awesome !! 

> 在 2018年7月9日，上午11:51，Huxing Zhang  写道：
> 
> Hi All,
> 
> I am happy to announce that Dubbo has reached 20k Github stars
> today[1], an important milestone for Dubbo.
> 
> Dubbo is the first Java project that reaches 20k Github stars[2] in
> Apache Software Foundation, the second most[3] in terms of all
> languages in the foundation.
> 
> Dubbo is open sources in 2012, till now, it is the most popular RPC
> framework in China, and has been adopted by many companies for their
> production system, including:
> 
> Internet companies:
> * Alibaba
> * Dangdang
> * Qunar
> * Netease
> * etc.
> 
> State-owned enterprises:
> * Industrial and Commercial Bank of China
> * China Telecom
> * China Life
> * etc.
> 
> More use case can be found at the homepage: http://dubbo.incubator.apache.org/
> 
> As an incubator project, the Dubbo PPMC will continue to make the
> community open and diverse, and we are more than happy to have
> everyone come to contribute, any question can be discussed on dev
> mailing list.
> 
> [1] https://github.com/apache/incubator-dubbo
> [2] 
> https://github.com/search?l=Java=desc=org%3Aapache=stars=Repositories
> [3] https://github.com/search?o=desc=org%3Aapache=stars=Repositories
> 
> -- 
> Best Regards！
> Huxing



smime.p7s
Description: S/MIME cryptographic signature

Re: 20k Github stars for Dubbo

[Andrea Del Bene]

Great job guys! Dubbo is a really interesting and promising project

On Mon, Jul 9, 2018 at 9:26 AM, xingxuechao 
wrote:

> Awesome !!
>
> > 在 2018年7月9日，上午11:51，Huxing Zhang  写道：
> >
> > Hi All,
> >
> > I am happy to announce that Dubbo has reached 20k Github stars
> > today[1], an important milestone for Dubbo.
> >
> > Dubbo is the first Java project that reaches 20k Github stars[2] in
> > Apache Software Foundation, the second most[3] in terms of all
> > languages in the foundation.
> >
> > Dubbo is open sources in 2012, till now, it is the most popular RPC
> > framework in China, and has been adopted by many companies for their
> > production system, including:
> >
> > Internet companies:
> > * Alibaba
> > * Dangdang
> > * Qunar
> > * Netease
> > * etc.
> >
> > State-owned enterprises:
> > * Industrial and Commercial Bank of China
> > * China Telecom
> > * China Life
> > * etc.
> >
> > More use case can be found at the homepage:
> http://dubbo.incubator.apache.org/
> >
> > As an incubator project, the Dubbo PPMC will continue to make the
> > community open and diverse, and we are more than happy to have
> > everyone come to contribute, any question can be discussed on dev
> > mailing list.
> >
> > [1] https://github.com/apache/incubator-dubbo
> > [2] https://github.com/search?l=Java=desc=org%3Aapache=
> stars=Repositories
> > [3] https://github.com/search?o=desc=org%3Aapache=stars;
> type=Repositories
> >
> > --
> > Best Regards！
> > Huxing
>
>


-- 
Andrea Del Bene.
Apache Wicket committer.

Proposal for Dubbo 3.0

[Liujie Qin]

  Hi All, Dubbo has become a excellent RPC framework with the efforts of
various partners in the community. However, in the process of development,
we found some shortcomings of Dubbo 2.x, which is listed as follows:

   - The maintainability is relatively poor. The code uses a lot of
   dynamically generated classes. It is difficult to understand and difficult
   to debug. The code hierarchy is not clear enough, and the calling logic is
   confusing. As an experienced Dubbo developer, sometimes it is difficult for
   me to sort out the calling process of Dubbo 2.x; the more developed, the
   more difficult it is to maintain, so it needs to be refactored in order to
   develop better.
   - Some extensions cannot meet current needs, such as service addresses
   push monitoring, performing Filter early interception requests before
   service addresses selection, printing the process of route selection, etc.
   - The underlying Dubbo 2.X is based on synchronous calls. The
   asynchronous call is wrapped synchronously. This introduces inaccuracies
   such as RT during asynchronous calls.
   - At present, the service metadata information and the address of the
   Dubbo service are coupled together. Most of the metadata is the same, and
   the metadata is redundant. At the same time, as the size of the machine
   increases, the Registry is under great pressure, especially when machine
   restart.
   - The service registry and the configuration center are coupled
   together, and after splitting, the management and storage of service
   governance rule data such as routing rules can be better handled.
   - The core is written based on JDK 1.6 and cannot use the newer JDK
   features. It is recommended to upgrade JDK to 1.8 and above.

For the above reasons, in order to better develop Dubbo and attract more
people to participate in the development of the Dubbo community, I propose
to refactor the Dubbo 2.x code. The newly developed version number is Dubbo
3.x. Refactoring Dubbo 3.x will have the following advantages:

   - Refactoring core modules to make the code more concise and
   understandable
   - Refactoring the routing process, Making the route process to Pipeline
   style,Making the route process can be observed
   - Add new extension points to make it easier for developers to extend
   the framework
   - Add the Service Domain Model to enable developers to handle its
   lifecycle
   - Supports asynchronous interface, unified call process returns
   CompleteFuture, synchronous call process uses CompleteFuture wrapper; Solve
   the problem of inaccurate statistics such as RT during asynchronous call
   - Splitting out the Configuration Center and Registry for better control
   and support for larger clusters
   - Prepare for new features such as Http2 stream、Reactive stream
   - Performance improvement
   - And so on

Of course, refactoring Dubbo 3.x also faces the following challenges:

   - A wide range of refactorings that can cause extension points to be
   incompatible
   - The Dubbo team may need to maintain two branches at the same time for
   a longer period of time

For the following challenges, we can do this:

   -

   For major extension points, such as Fitler, etc., be sure to ensure
   compatibility and enable developers to smoothly upgrade
   -

   For some extension points, the Dubbo team will listen to the community
   and selectively fix compatibility issues with some extension points.

Comments welcome!

thank you ~

avro serialization implement

[wu tianbiao]

Hi all,

I post a PR for avro serialization implement. URL: 
https://github.com/apache/incubator-dubbo/pull/1994

As @chickenlj mention, so send an mail here to 
discuss whether to remove this extension to the ecos.

Re: 20k Github stars for Dubbo

[Shalitha Suranga]

Awesome!! congrats

On Mon, Jul 9, 2018 at 12:39 PM Prateek Chanda 
wrote:

> Congratulations!!  Maybe I can contribute to it when I get free time.
>
> Prateek
>
>
>
> On 9 July 2018 at 12:15, Zhanhui Li  wrote:
>
> > Congratulations!
> >
> > > 在 2018年7月9日，下午2:42，Mercy  写道：
> > >
> > > Great Job!
> > >
> > >
> > > Kind regards,
> > >
> > > Mercy
> > >
> > >
> > > 在 2018/7/9 上午11:51, Huxing Zhang 写道:
> > >> Hi All,
> > >>
> > >> I am happy to announce that Dubbo has reached 20k Github stars
> > >> today[1], an important milestone for Dubbo.
> > >>
> > >> Dubbo is the first Java project that reaches 20k Github stars[2] in
> > >> Apache Software Foundation, the second most[3] in terms of all
> > >> languages in the foundation.
> > >>
> > >> Dubbo is open sources in 2012, till now, it is the most popular RPC
> > >> framework in China, and has been adopted by many companies for their
> > >> production system, including:
> > >>
> > >> Internet companies:
> > >> * Alibaba
> > >> * Dangdang
> > >> * Qunar
> > >> * Netease
> > >> * etc.
> > >>
> > >> State-owned enterprises:
> > >> * Industrial and Commercial Bank of China
> > >> * China Telecom
> > >> * China Life
> > >> * etc.
> > >>
> > >> More use case can be found at the homepage:
> > http://dubbo.incubator.apache.org/
> > >>
> > >> As an incubator project, the Dubbo PPMC will continue to make the
> > >> community open and diverse, and we are more than happy to have
> > >> everyone come to contribute, any question can be discussed on dev
> > >> mailing list.
> > >>
> > >> [1] https://github.com/apache/incubator-dubbo
> > >> [2] https://github.com/search?l=Java=desc=org%3Aapache=
> > stars=Repositories
> > >> [3] https://github.com/search?o=desc=org%3Aapache=stars;
> > type=Repositories
> > >>
> > >
> > >
> > >
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > For additional commands, e-mail: dev-h...@community.apache.org
> >
> >
>


-- 
Regards,

*Shalitha Suranga Bsc. CS (UG)*
www.shalithasuranga.me

Re: 20k Github stars for Dubbo

[Li,De(BDG)]

It’s great, congratulations!

On 2018/7/9 下午3:22， "Xin Wang"  wrote:

>Awesome
>
>Zhanhui Li  于2018年7月9日周一 下午2:52写道：
>
>> Congratulations!
>>
>> > 在 2018年7月9日，下午2:42，Mercy  写道：
>> >
>> > Great Job!
>> >
>> >
>> > Kind regards,
>> >
>> > Mercy
>> >
>> >
>> > 在 2018/7/9 上午11:51, Huxing Zhang 写道:
>> >> Hi All,
>> >>
>> >> I am happy to announce that Dubbo has reached 20k Github stars
>> >> today[1], an important milestone for Dubbo.
>> >>
>> >> Dubbo is the first Java project that reaches 20k Github stars[2] in
>> >> Apache Software Foundation, the second most[3] in terms of all
>> >> languages in the foundation.
>> >>
>> >> Dubbo is open sources in 2012, till now, it is the most popular RPC
>> >> framework in China, and has been adopted by many companies for their
>> >> production system, including:
>> >>
>> >> Internet companies:
>> >> * Alibaba
>> >> * Dangdang
>> >> * Qunar
>> >> * Netease
>> >> * etc.
>> >>
>> >> State-owned enterprises:
>> >> * Industrial and Commercial Bank of China
>> >> * China Telecom
>> >> * China Life
>> >> * etc.
>> >>
>> >> More use case can be found at the homepage:
>> http://dubbo.incubator.apache.org/
>> >>
>> >> As an incubator project, the Dubbo PPMC will continue to make the
>> >> community open and diverse, and we are more than happy to have
>> >> everyone come to contribute, any question can be discussed on dev
>> >> mailing list.
>> >>
>> >> [1] https://github.com/apache/incubator-dubbo
>> >> [2]
>> 
>>https://github.com/search?l=Java=desc=org%3Aapache=stars=Repos
>>itories
>> >> [3]
>> 
>>https://github.com/search?o=desc=org%3Aapache=stars=Repositories
>> >>
>> >
>> >
>> >
>> > -
>> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> > For additional commands, e-mail: general-h...@incubator.apache.org
>>
>>
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>>

Re: 20k Github stars for Dubbo

[Mercy]

Great Job!


Kind regards,

Mercy


在 2018/7/9 上午11:51, Huxing Zhang 写道:

Hi All,

I am happy to announce that Dubbo has reached 20k Github stars
today[1], an important milestone for Dubbo.

Dubbo is the first Java project that reaches 20k Github stars[2] in
Apache Software Foundation, the second most[3] in terms of all
languages in the foundation.

Dubbo is open sources in 2012, till now, it is the most popular RPC
framework in China, and has been adopted by many companies for their
production system, including:

Internet companies:
* Alibaba
* Dangdang
* Qunar
* Netease
* etc.

State-owned enterprises:
* Industrial and Commercial Bank of China
* China Telecom
* China Life
* etc.

More use case can be found at the homepage: http://dubbo.incubator.apache.org/

As an incubator project, the Dubbo PPMC will continue to make the
community open and diverse, and we are more than happy to have
everyone come to contribute, any question can be discussed on dev
mailing list.

[1] https://github.com/apache/incubator-dubbo
[2] 
https://github.com/search?l=Java=desc=org%3Aapache=stars=Repositories
[3] https://github.com/search?o=desc=org%3Aapache=stars=Repositories

Re: 20k Github stars for Dubbo

[Zhanhui Li]

Congratulations!

> 在 2018年7月9日，下午2:42，Mercy  写道：
> 
> Great Job!
> 
> 
> Kind regards,
> 
> Mercy
> 
> 
> 在 2018/7/9 上午11:51, Huxing Zhang 写道:
>> Hi All,
>> 
>> I am happy to announce that Dubbo has reached 20k Github stars
>> today[1], an important milestone for Dubbo.
>> 
>> Dubbo is the first Java project that reaches 20k Github stars[2] in
>> Apache Software Foundation, the second most[3] in terms of all
>> languages in the foundation.
>> 
>> Dubbo is open sources in 2012, till now, it is the most popular RPC
>> framework in China, and has been adopted by many companies for their
>> production system, including:
>> 
>> Internet companies:
>> * Alibaba
>> * Dangdang
>> * Qunar
>> * Netease
>> * etc.
>> 
>> State-owned enterprises:
>> * Industrial and Commercial Bank of China
>> * China Telecom
>> * China Life
>> * etc.
>> 
>> More use case can be found at the homepage: 
>> http://dubbo.incubator.apache.org/
>> 
>> As an incubator project, the Dubbo PPMC will continue to make the
>> community open and diverse, and we are more than happy to have
>> everyone come to contribute, any question can be discussed on dev
>> mailing list.
>> 
>> [1] https://github.com/apache/incubator-dubbo
>> [2] 
>> https://github.com/search?l=Java=desc=org%3Aapache=stars=Repositories
>> [3] https://github.com/search?o=desc=org%3Aapache=stars=Repositories
>> 
> 
> 
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org

Re: Proposal for Dubbo 3.0

[Huxing Zhang]

Hi,

On Mon, Jul 9, 2018 at 3:32 PM, Liujie Qin  wrote:
>   Hi All, Dubbo has become a excellent RPC framework with the efforts of
> various partners in the community. However, in the process of development,
> we found some shortcomings of Dubbo 2.x, which is listed as follows:
>
>- The maintainability is relatively poor. The code uses a lot of
>dynamically generated classes. It is difficult to understand and difficult
>to debug. The code hierarchy is not clear enough, and the calling logic is
>confusing. As an experienced Dubbo developer, sometimes it is difficult for
>me to sort out the calling process of Dubbo 2.x; the more developed, the
>more difficult it is to maintain, so it needs to be refactored in order to
>develop better.
>- Some extensions cannot meet current needs, such as service addresses
>push monitoring, performing Filter early interception requests before
>service addresses selection, printing the process of route selection, etc.
>- The underlying Dubbo 2.X is based on synchronous calls. The
>asynchronous call is wrapped synchronously. This introduces inaccuracies
>such as RT during asynchronous calls.
>- At present, the service metadata information and the address of the
>Dubbo service are coupled together. Most of the metadata is the same, and
>the metadata is redundant. At the same time, as the size of the machine
>increases, the Registry is under great pressure, especially when machine
>restart.

+1 to separate service registration data and service configuration data.

>- The service registry and the configuration center are coupled
>together, and after splitting, the management and storage of service
>governance rule data such as routing rules can be better handled.
>- The core is written based on JDK 1.6 and cannot use the newer JDK
>features. It is recommended to upgrade JDK to 1.8 and above.

+1 to rewrite Dubbo using 1.8

>
> For the above reasons, in order to better develop Dubbo and attract more
> people to participate in the development of the Dubbo community, I propose
> to refactor the Dubbo 2.x code. The newly developed version number is Dubbo
> 3.x. Refactoring Dubbo 3.x will have the following advantages:
>
>- Refactoring core modules to make the code more concise and
>understandable
>- Refactoring the routing process, Making the route process to Pipeline
>style,Making the route process can be observed
>- Add new extension points to make it easier for developers to extend
>the framework
>- Add the Service Domain Model to enable developers to handle its
>lifecycle
>- Supports asynchronous interface, unified call process returns
>CompleteFuture, synchronous call process uses CompleteFuture wrapper; Solve
>the problem of inaccurate statistics such as RT during asynchronous call
>- Splitting out the Configuration Center and Registry for better control
>and support for larger clusters
>- Prepare for new features such as Http2 stream、Reactive stream

Strong +1

>- Performance improvement
>- And so on
>
> Of course, refactoring Dubbo 3.x also faces the following challenges:
>
>- A wide range of refactorings that can cause extension points to be
>incompatible
>- The Dubbo team may need to maintain two branches at the same time for
>a longer period of time

If there were 3.x, we will have:

* 2.5.x: Java 6+
* 2.6.x: Java 6+
* 2.7.x: Java 8+
* 3.0.x: Java 8+

What is the difference between 2.7.x and 3.0.x?

>
> For the following challenges, we can do this:
>
>-
>
>For major extension points, such as Fitler, etc., be sure to ensure
>compatibility and enable developers to smoothly upgrade
>-
>
>For some extension points, the Dubbo team will listen to the community
>and selectively fix compatibility issues with some extension points.

I suggest we note down all the incompatible changes and provide a
migration guide for them.


>
> Comments welcome!
>
> thank you ~



-- 
Best Regards！
Huxing

Re: 20k Github stars for Dubbo

[???? Sheng Wu]

Good for the project and community. Congrats.


If you are going to do service mesh component, let's discuss how SkyWalking 
works on your Mesher control panel, even data panel. I have already started to 
discuss this with Ant Finance team and Istio team. I heard some rumors that you 
are doing this right now. Glad to work together.


And Congrats again. Wonderful work.


--
Sheng Wu
Apache SkyWalking 


 




-- Original --
From:  "Li,De(BDG)";
Date:  Mon, Jul 9, 2018 04:49 PM
To:  "gene...@incubator.apache.org";
Cc:  "dev@dubbo.apache.org"; 
"hux...@apache.org"; 
"d...@community.apache.org"; 
Subject:  Re: 20k Github stars for Dubbo



It??s great, congratulations!

On 2018/7/9 3:22?? "Xin Wang"  wrote:

>Awesome
>
>Zhanhui Li  ??2018??7??9?? 2:52??
>
>> Congratulations!
>>
>> > ?? 2018??7??92:42??Mercy  ??
>> >
>> > Great Job!
>> >
>> >
>> > Kind regards,
>> >
>> > Mercy
>> >
>> >
>> > ?? 2018/7/9 11:51, Huxing Zhang :
>> >> Hi All,
>> >>
>> >> I am happy to announce that Dubbo has reached 20k Github stars
>> >> today[1], an important milestone for Dubbo.
>> >>
>> >> Dubbo is the first Java project that reaches 20k Github stars[2] in
>> >> Apache Software Foundation, the second most[3] in terms of all
>> >> languages in the foundation.
>> >>
>> >> Dubbo is open sources in 2012, till now, it is the most popular RPC
>> >> framework in China, and has been adopted by many companies for their
>> >> production system, including:
>> >>
>> >> Internet companies:
>> >> * Alibaba
>> >> * Dangdang
>> >> * Qunar
>> >> * Netease
>> >> * etc.
>> >>
>> >> State-owned enterprises:
>> >> * Industrial and Commercial Bank of China
>> >> * China Telecom
>> >> * China Life
>> >> * etc.
>> >>
>> >> More use case can be found at the homepage:
>> http://dubbo.incubator.apache.org/
>> >>
>> >> As an incubator project, the Dubbo PPMC will continue to make the
>> >> community open and diverse, and we are more than happy to have
>> >> everyone come to contribute, any question can be discussed on dev
>> >> mailing list.
>> >>
>> >> [1] https://github.com/apache/incubator-dubbo
>> >> [2]
>> 
>>https://github.com/search?l=Java=desc=org%3Aapache=stars=Repos
>>itories
>> >> [3]
>> 
>>https://github.com/search?o=desc=org%3Aapache=stars=Repositories
>> >>
>> >
>> >
>> >
>> > -
>> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> > For additional commands, e-mail: general-h...@incubator.apache.org
>>
>>
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>>


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[DISCUSS]Enhancements of the async programming model.

[jun liu]

Hi All, 

I have submitted a PR[1] improving the async programming model exists in Dubbo, 
the PR has been opened for days. Since the changes involved are relatively 
large, I kindly ask for your suggestions and reviews. To make sure you fully 
understand what the PR promotes, here’s an article[2] describing the design 
principles and how you can use it. Unfortunately, the article only have a 
Chinese version at present.

1. https://github.com/apache/incubator-dubbo/pull/1957
2. 
https://github.com/chickenlj/incubator-dubbo/wiki/%E5%A6%82%E4%BD%95%E5%9F%BA%E4%BA%8EDubbo%E5%AE%9E%E7%8E%B0%E5%85%A8%E5%BC%82%E6%AD%A5%E8%B0%83%E7%94%A8%E9%93%BE

Best regards,
Jun

CI and JavaDoc

[Andrea Del Bene]

Hi Dubbers!

I know you are super busy-at the moment, but I'd like to add to your TODO
list a task to host Dubbo JavaDoc on your Apache site. At the moment
JavaDocs are available at http://www.javadoc.io but it would be nice to
host them in-house. Normally this is done on the CI server at the end of
the build coping javadoc files to the site server.

Thank you in advance

Andrea Del Bene.
Apache Wicket committer.

??????dubbo??????????2.6.2????????

[??????]

You can debug when  dubbo start to see why doesn't work




| |
??
??kimmk...@163.com
|

??  

??2018??07??13?? 16:52?? ??
dubbo2.6.0dubbocom.alibaba:dubbo:2.6.02.6.2com.alibaba:dubbo:2.6.2??provider??consumer??war??

??

Re: dubbo无法升级到2.6.2进行使用

[Huxing Zhang]

Hi，

First, ensure your application is working correctly. If you are
deploying Dubbo application on a servlet container like Tomcat, make
sure it the web application is deployed successfully.
You mentioned that your war is not deployed well, so please check the
servlet container log first.
e.g. If you are running Tomcat, check the catalina.out and
localhost.log  to see if there is any error.

2018-07-13 16:52 GMT+08:00 光辉岁月 <122260...@qq.com>:
> 各位大佬，咨询个问题，业务组件依赖的dubbo想做次升级，发现依赖2.6.0版本dubbo业务组件（引用了com.alibaba:dubbo:2.6.0）可以正常使用，依赖2.6.2版本com.alibaba:dubbo:2.6.2，业务组件没法正常使用，具体现象为相关provider、consumer也没有全部注册到注册中心，war实例没有正常启动。
>
> 后台未报任何错误，不知道怎么排查。。。还望帮忙给些建议方案



-- 
Best Regards！
Huxing

Re: [ANNOUNCE] Welcome new committer Minxuan Zhuang

[Zonghai Shang]

Congratulations!

yiji

yuhang xiu  于2018年9月12日周三 上午10:09写道：

> Congratulations!
> Welcome to Dubbo. :)
>
> Huxing Zhang  于2018年9月12日周三 上午7:26写道：
>
> > Congratulations!
> > On Tue, Sep 11, 2018 at 8:39 PM Jun Liu  wrote:
> > >
> > > Hi, Community,
> > >
> > > On behalf of the Dubbo PPMC, I am pleased to announce that Minxuan
> > Zhuang, whose github id is nzomkxia, has been voted in as a new Dubbo
> > committer.
> > >
> > > He has did and is doing a great job on dubbo-ops, and I just want to
> say
> > thanks and congratulations. Please join me to say congratulations to
> > Minxuan!
> > >
> > > Minxuan, would you please briefly introduce yourself to the community?
> > >
> > > Best regards,
> > > Jun
> > >
> >
> >
> > --
> > Best Regards！
> > Huxing
> >
>

Re: [ANNOUNCE] 2.6.3 has been released.

[jun liu]

Huxing,

> Source release:
> https://www.apache.org/dyn/closer.cgi?path=incubator/dubbo/2.6.3/apache-dubbo-incubating-2.6.3-source-release.zip
> Binary release:
> https://www.apache.org/dyn/closer.cgi?path=incubator/dubbo/2.6.3/apache-dubbo-incubating-2.6.3-bin-release
>  
> 
Where are we going to add this links?

Best regards,
Jun

> On 12 Sep 2018, at 07:34, Huxing Zhang  wrote:
> 
> Glad to hear that!
> 
> There is one more thing to do: add download link to the official ASF release.
> 
> Source release:
> https://www.apache.org/dyn/closer.cgi?path=incubator/dubbo/2.6.3/apache-dubbo-incubating-2.6.3-source-release.zip
> Binary release:
> https://www.apache.org/dyn/closer.cgi?path=incubator/dubbo/2.6.3/apache-dubbo-incubating-2.6.3-bin-release.zip
> 
> On Tue, Sep 11, 2018 at 8:10 PM Jun Liu  wrote:
>> 
>> Hi Community,
>> 
>> I am pleased to announce that the 2.6.3 version has just been released. Both 
>> the source release[1] and the maven binary release[2] are available now, you 
>> can also find the detailed release notes in here[3] or quickly check the 
>> important changes I list below:
>> * Delivery of attachments from provider to consumer.
>> * Generic invoke and attachments for http protocol.
>> * Introduce new bootstrap module
>> * Performance tuning
>> * Bugfixes
>> 
>> Normally, you can smoothly upgrade to the new version from any version 
>> before 2.6.2 without having to do too many changes to your apps and without 
>> having to worry about any incompatible problems.
>> If you have any usage questions, or have problems when upgrading or find any 
>> problems about enhancements included in this release, please don’t hesitate 
>> to let us know by sending feedback to this mailing list or filing an issue 
>> on github[4].
>> 
>> 1. https://dist.apache.org/repos/dist/release/incubator/dubbo/2.6.3/
>> 2. http://central.maven.org/maven2/com/alibaba/
>> 3. https://github.com/apache/incubator-dubbo/releases
>> 4. https://github.com/apache/incubator-dubbo/issues
>> 
>> Best regards,
>> Jun
>> 
> 
> 
> -- 
> Best Regards！
> Huxing

Re: Local forced trigger mock does not take effect

[Zonghai Shang]

> 1. Improve the documentation
> 2. Consider the configuration of xml compatible with the configuration of
the override protocol

I agree, maybe a pull request to fix it.

Best regards,
yiji

yuhang xiu  于2018年9月12日周三 上午10:36写道：

> Hi guys,
>
> I also encountered this confusion when I configured the mock in xml.
> Now it seems that the form of mock=force:return xxx can only be used when
> dynamically configured using the override protocol, which does not match
> the configuration of the xml.
>
> I think we need to do one of the following two things:
> 1. Improve the documentation
> 2. Consider the configuration of xml compatible with the configuration of
> the override protocol
>
> Zonghai Shang  于2018年9月12日周三 上午10:24写道：
>
> > > 1. mock=“true”, this will direct the to the default mock implementation
> > with a name convention like DemoServiceMock.
> > > 3. mock=“org.apache.dubbo.xxx.xxxMock”, specify the class where your
> mock
> > logic is located.
> >
> > mock=“org.apache.dubbo.xxx.xxxMock” , only throw RpcException to execute
> > the mock, which does not match the force logic.
> >
> > > 2. mock=“force:return xxx”, directly specify the return value you want.
> > This may be the case you want to use, but I think you just forget the
> mock
> > value you want.
> >
> > It does’t work, cause:
> > PropertyAccessException 1:
> > org.springframework.beans.MethodInvocationException: Property 'mock'
> threw
> > exception; nested exception is java.lang.IllegalStateException: Invalid
> > mock="force:return null" contain illegal charactor, only digit, letter,
> > '-', '_' and '.' is legal.
> >
> > I think maybe the implementation of mock may have bugs.
> >
> >
> > Best regards,
> > yiji
> >
> > jun liu  于2018年9月12日周三 上午8:56写道：
> >
> > > >  > > > interface="com.alibaba.dubbo.samples.mock.api.DemoService"
> > mock="force”/>
> > >
> > > As far as I can describe now, I think you can use:
> > > 1. mock=“true”, this will direct the to the default mock implementation
> > > with a name convention like DemoServiceMock.
> > > 2. mock=“force:return xxx”, directly specify the return value you want.
> > > This may be the case you want to use, but I think you just forget the
> > mock
> > > value you want.
> > > 3. mock=“org.apache.dubbo.xxx.xxxMock”, specify the class where your
> mock
> > > logic is located.
> > >
> > > > `com.alibaba.dubbo.common.utils.ConfigUtils#isDefault` should support
> > > > force? Can someone help me?
> > >
> > > Given the above usage supported I think there’s no need to add an extra
> > > mock=“force” support. What do u think?
> > >
> > > Best regards,
> > > Jun
> > >
> > > > On 11 Sep 2018, at 16:31, Zonghai Shang  wrote:
> > > >
> > > > Hi,
> > > >
> > > > MockClusterInvoker provides local forced mock，I tested it locally,
> but
> > it
> > > > doesn't work.
> > > >
> > > > @Override
> > > > public Result invoke(Invocation invocation) throws RpcException {
> > > >// ….
> > > >else if (value.startsWith("force")) {
> > > >if (logger.isWarnEnabled()) {
> > > >logger.info("force-mock: " + invocation.getMethodName()
> + "
> > > > force-mock enabled , url : " + directory.getUrl());
> > > >}
> > > >//force:direct mock
> > > >result = doMockInvoke(invocation, null);
> > > >}
> > > >   // ….
> > > > }
> > > >
> > > >  > > > interface="com.alibaba.dubbo.samples.mock.api.DemoService"
> > mock="force”/>
> > > >
> > > > Here is demo:
> > > >
> https://github.com/dubbo/dubbo-samples/tree/master/dubbo-samples-mock
> > > >
> > > > `com.alibaba.dubbo.common.utils.ConfigUtils#isDefault` should support
> > > > force? Can someone help me?
> > > >
> > > > yiji
> > >
> > >
> >
>

Re: Local forced trigger mock does not take effect

[jun liu]

>  interface="com.alibaba.dubbo.samples.mock.api.DemoService" mock="force”/>

As far as I can describe now, I think you can use:
1. mock=“true”, this will direct the to the default mock implementation with a 
name convention like DemoServiceMock.
2. mock=“force:return xxx”, directly specify the return value you want. This 
may be the case you want to use, but I think you just forget the mock value you 
want.
3. mock=“org.apache.dubbo.xxx.xxxMock”, specify the class where your mock logic 
is located.

> `com.alibaba.dubbo.common.utils.ConfigUtils#isDefault` should support
> force? Can someone help me?

Given the above usage supported I think there’s no need to add an extra 
mock=“force” support. What do u think?

Best regards,
Jun

> On 11 Sep 2018, at 16:31, Zonghai Shang  wrote:
> 
> Hi,
> 
> MockClusterInvoker provides local forced mock，I tested it locally, but it
> doesn't work.
> 
> @Override
> public Result invoke(Invocation invocation) throws RpcException {
>// ….
>else if (value.startsWith("force")) {
>if (logger.isWarnEnabled()) {
>logger.info("force-mock: " + invocation.getMethodName() + "
> force-mock enabled , url : " + directory.getUrl());
>}
>//force:direct mock
>result = doMockInvoke(invocation, null);
>}
>   // ….
> }
> 
>  interface="com.alibaba.dubbo.samples.mock.api.DemoService" mock="force”/>
> 
> Here is demo:
> https://github.com/dubbo/dubbo-samples/tree/master/dubbo-samples-mock
> 
> `com.alibaba.dubbo.common.utils.ConfigUtils#isDefault` should support
> force? Can someone help me?
> 
> yiji

Re: Local forced trigger mock does not take effect

[Zonghai Shang]

> 1. mock=“true”, this will direct the to the default mock implementation
with a name convention like DemoServiceMock.
> 3. mock=“org.apache.dubbo.xxx.xxxMock”, specify the class where your mock
logic is located.

mock=“org.apache.dubbo.xxx.xxxMock” , only throw RpcException to execute
the mock, which does not match the force logic.

> 2. mock=“force:return xxx”, directly specify the return value you want.
This may be the case you want to use, but I think you just forget the mock
value you want.

It does’t work, cause:
PropertyAccessException 1:
org.springframework.beans.MethodInvocationException: Property 'mock' threw
exception; nested exception is java.lang.IllegalStateException: Invalid
mock="force:return null" contain illegal charactor, only digit, letter,
'-', '_' and '.' is legal.

I think maybe the implementation of mock may have bugs.


Best regards,
yiji

jun liu  于2018年9月12日周三 上午8:56写道：

> >  > interface="com.alibaba.dubbo.samples.mock.api.DemoService" mock="force”/>
>
> As far as I can describe now, I think you can use:
> 1. mock=“true”, this will direct the to the default mock implementation
> with a name convention like DemoServiceMock.
> 2. mock=“force:return xxx”, directly specify the return value you want.
> This may be the case you want to use, but I think you just forget the mock
> value you want.
> 3. mock=“org.apache.dubbo.xxx.xxxMock”, specify the class where your mock
> logic is located.
>
> > `com.alibaba.dubbo.common.utils.ConfigUtils#isDefault` should support
> > force? Can someone help me?
>
> Given the above usage supported I think there’s no need to add an extra
> mock=“force” support. What do u think?
>
> Best regards,
> Jun
>
> > On 11 Sep 2018, at 16:31, Zonghai Shang  wrote:
> >
> > Hi,
> >
> > MockClusterInvoker provides local forced mock，I tested it locally, but it
> > doesn't work.
> >
> > @Override
> > public Result invoke(Invocation invocation) throws RpcException {
> >// ….
> >else if (value.startsWith("force")) {
> >if (logger.isWarnEnabled()) {
> >logger.info("force-mock: " + invocation.getMethodName() + "
> > force-mock enabled , url : " + directory.getUrl());
> >}
> >//force:direct mock
> >result = doMockInvoke(invocation, null);
> >}
> >   // ….
> > }
> >
> >  > interface="com.alibaba.dubbo.samples.mock.api.DemoService" mock="force”/>
> >
> > Here is demo:
> > https://github.com/dubbo/dubbo-samples/tree/master/dubbo-samples-mock
> >
> > `com.alibaba.dubbo.common.utils.ConfigUtils#isDefault` should support
> > force? Can someone help me?
> >
> > yiji
>
>

Re: 关于dubbo的版本

[Zonghai Shang]

Welcome, github: https://github.com/apache/incubator-dubbo

yiji

宗荣  于2018年9月12日周三 上午11:06写道：

> http://mvnrepository.com/artifact/com.alibaba/dubbo
> 这个是dubbo版本的官方地址吗，里面的最新版本是2.6.3，但我看网上有一些版本已经到了2.8.4，我是一名刚开始学习dubbo的开发人员，不知能否帮忙解答下，谢谢！

Re: current status of dubbo ops

[Huxing Zhang]

On Mon, Sep 10, 2018 at 11:36 PM Minxuan Zhuang  wrote:
>
> dubbo ops is under refactoring, here is some progress status:
> 1 the current working branch is *develop*,
> 2 the monitor and registry module have been removed

Just want to confirm, do you mean that dubbo-monitor has been removed?
If so, where have it been moved to?

> 3 prototype of 'service search' and 'routing rule' are accomplished
> 4. new readme about how to build the front end and back end
>
> if you are interested in this project, please consider to accomplish
> service governance pages(dynamic config, load balance, etc.), the layout is
> similar with the current routing rule page, and submit pr to develop
> branch, thanks

My suggestions:

1. ask the Infra to make the develop branch as default branch. You can
file ticket in JIRA, examples [1].
2. make the community involvement trackable, there are several ways:
   a) add a TODO list to Github, with some detailed actionable item so
that people could catch up,
   b) using "Project",
   c) create several issues, with labels "Help wanted".
Among them I prefer b), but let's see how others think.
3. remember to complete the ip clearance of this project, e.g. change
the package name to org.apache.
4. Enrich the README file, currently it only contains the build
instruction, maybe adding some screenshot to introduce the features?


[1] https://issues.apache.org/jira/browse/INFRA-16451

-- 
Best Regards！
Huxing

Re: Travis CI failed

[Jerrick Zhu]

When I enabled -X, I didn't get any useful informations. Neither upgrading
maven-compile-plugin.
After that I wanted to remove it in .m2, so removing the cache
configuration.

Until now I do not find out the reason.

On Wed, Sep 12, 2018 at 7:37 AM Huxing Zhang  wrote:

> Hi,
>
> On Tue, Sep 11, 2018 at 11:41 AM Jerrick Zhu  wrote:
> >
> > I try to remove the cache in .travis.yml,
> >
> > ```
> > cache:
> > directories:
> > - '$HOME/.m2/repository'
> > ```
>
> I have also tried a few times. How did you find it out? Are you using
> maven -X for debugging?
>
> >
> > Now it works. Maybe the cache affects the build process.
> >
> > I'll file a PR on master.
> >
> > On Mon, Sep 10, 2018 at 4:57 PM Jerrick Zhu  wrote:
> >
> > > I tried to restart the build for a few times, it failed with the same
> > > error.
> > >
> > > On Mon, Sep 10, 2018 at 1:56 PM yuhang xiu  wrote:
> > >
> > >> Hi,
> > >> I also checked the log just now and found no problems. I have
> restarted
> > >> this task, I will observe the results after a while.
> > >>
> > >> YunKun Huang  于2018年9月10日周一 下午1:53写道：
> > >>
> > >> > Check this log, it says compile fail on dubbo-common module:
> > >> > https://travis-ci.org/apache/incubator-dubbo/jobs/426109384
> > >> >
> > >> > But there is no code change since latest successful bulid.
> > >> > Also I try to run build in my local, it pass with jdk 8.
> > >> >
> > >> > On 2018/09/10 05:36:27, Jerrick Zhu  wrote:
> > >> > > Hi, community
> > >> > >
> > >> > > I found that all travis CI builds failed on Java8.
> > >> > >
> > >> > > Here is the master's build:
> > >> https://travis-ci.org/apache/incubator-dubbo
> > >> > >
> > >> > > Anyone can help to check it?
> > >> > >
> > >> >
> > >>
> > >
>
>
>
> --
> Best Regards！
> Huxing
>

Re: Local forced trigger mock does not take effect

[jun liu]

>> 2. mock=“force:return xxx”, directly specify the return value you want.
> This may be the case you want to use, but I think you just forget the mock
> value you want.
> 
> It does’t work, cause:
> PropertyAccessException 1:
> org.springframework.beans.MethodInvocationException: Property 'mock' threw
> exception; nested exception is java.lang.IllegalStateException: Invalid
> mock="force:return null" contain illegal charactor, only digit, letter,
> '-', '_' and '.' is legal.
> 
> I think maybe the implementation of mock may have bugs.

I haven’t tried this usage in xml yet, seems like we need to find the problem 
and fix it so that it can work properly as expected.

Best regards,
Jun

> On 12 Sep 2018, at 10:24, Zonghai Shang  wrote:
> 
>> 1. mock=“true”, this will direct the to the default mock implementation
> with a name convention like DemoServiceMock.
>> 3. mock=“org.apache.dubbo.xxx.xxxMock”, specify the class where your mock
> logic is located.
> 
> mock=“org.apache.dubbo.xxx.xxxMock” , only throw RpcException to execute
> the mock, which does not match the force logic.
> 
>> 2. mock=“force:return xxx”, directly specify the return value you want.
> This may be the case you want to use, but I think you just forget the mock
> value you want.
> 
> It does’t work, cause:
> PropertyAccessException 1:
> org.springframework.beans.MethodInvocationException: Property 'mock' threw
> exception; nested exception is java.lang.IllegalStateException: Invalid
> mock="force:return null" contain illegal charactor, only digit, letter,
> '-', '_' and '.' is legal.
> 
> I think maybe the implementation of mock may have bugs.
> 
> 
> Best regards,
> yiji
> 
> jun liu  于2018年9月12日周三 上午8:56写道：
> 
>>> >> interface="com.alibaba.dubbo.samples.mock.api.DemoService" mock="force”/>
>> 
>> As far as I can describe now, I think you can use:
>> 1. mock=“true”, this will direct the to the default mock implementation
>> with a name convention like DemoServiceMock.
>> 2. mock=“force:return xxx”, directly specify the return value you want.
>> This may be the case you want to use, but I think you just forget the mock
>> value you want.
>> 3. mock=“org.apache.dubbo.xxx.xxxMock”, specify the class where your mock
>> logic is located.
>> 
>>> `com.alibaba.dubbo.common.utils.ConfigUtils#isDefault` should support
>>> force? Can someone help me?
>> 
>> Given the above usage supported I think there’s no need to add an extra
>> mock=“force” support. What do u think?
>> 
>> Best regards,
>> Jun
>> 
>>> On 11 Sep 2018, at 16:31, Zonghai Shang  wrote:
>>> 
>>> Hi,
>>> 
>>> MockClusterInvoker provides local forced mock，I tested it locally, but it
>>> doesn't work.
>>> 
>>> @Override
>>> public Result invoke(Invocation invocation) throws RpcException {
>>>   // ….
>>>   else if (value.startsWith("force")) {
>>>   if (logger.isWarnEnabled()) {
>>>   logger.info("force-mock: " + invocation.getMethodName() + "
>>> force-mock enabled , url : " + directory.getUrl());
>>>   }
>>>   //force:direct mock
>>>   result = doMockInvoke(invocation, null);
>>>   }
>>>  // ….
>>> }
>>> 
>>> >> interface="com.alibaba.dubbo.samples.mock.api.DemoService" mock="force”/>
>>> 
>>> Here is demo:
>>> https://github.com/dubbo/dubbo-samples/tree/master/dubbo-samples-mock
>>> 
>>> `com.alibaba.dubbo.common.utils.ConfigUtils#isDefault` should support
>>> force? Can someone help me?
>>> 
>>> yiji
>> 
>> 

Re: Travis CI failed

[Huxing Zhang]

Hi,

On Tue, Sep 11, 2018 at 11:41 AM Jerrick Zhu  wrote:
>
> I try to remove the cache in .travis.yml,
>
> ```
> cache:
> directories:
> - '$HOME/.m2/repository'
> ```

I have also tried a few times. How did you find it out? Are you using
maven -X for debugging?

>
> Now it works. Maybe the cache affects the build process.
>
> I'll file a PR on master.
>
> On Mon, Sep 10, 2018 at 4:57 PM Jerrick Zhu  wrote:
>
> > I tried to restart the build for a few times, it failed with the same
> > error.
> >
> > On Mon, Sep 10, 2018 at 1:56 PM yuhang xiu  wrote:
> >
> >> Hi,
> >> I also checked the log just now and found no problems. I have restarted
> >> this task, I will observe the results after a while.
> >>
> >> YunKun Huang  于2018年9月10日周一 下午1:53写道：
> >>
> >> > Check this log, it says compile fail on dubbo-common module:
> >> > https://travis-ci.org/apache/incubator-dubbo/jobs/426109384
> >> >
> >> > But there is no code change since latest successful bulid.
> >> > Also I try to run build in my local, it pass with jdk 8.
> >> >
> >> > On 2018/09/10 05:36:27, Jerrick Zhu  wrote:
> >> > > Hi, community
> >> > >
> >> > > I found that all travis CI builds failed on Java8.
> >> > >
> >> > > Here is the master's build:
> >> https://travis-ci.org/apache/incubator-dubbo
> >> > >
> >> > > Anyone can help to check it?
> >> > >
> >> >
> >>
> >



-- 
Best Regards！
Huxing

Re: The effect of Provider async on the Consumer side

[Huxing Zhang]

On Mon, Sep 10, 2018 at 10:10 AM yuhang xiu  wrote:
>
> Hi Huxing,
> This is because there is a bug that causes them to be inconsistent. We
> removed the async attribute from the Provider in ClusterUtil, but did not
> remove the method.async attribute, causing the Provider's method.async to
> affect the Consumer side.
>
> We don't need extra configuration, we just need to remove method.async in
> ClusterUtil to solve this problem, and we don't need to modify the URL of
> the Provider registered in the registry.


Thanks for the explanation, it looks good to me!

>
> Huxing Zhang  于2018年9月7日周五 下午11:40写道：
>
> > Hi,
> >
> > On Wed, Sep 5, 2018 at 3:30 PM yuhang xiu  wrote:
> > >
> > > Hi community,
> > >
> > > Recently I found a bug[1] in the issue list (submitted by the
> > > https://github.com/fingthinking user), which has been verified to be
> > valid.
> > > The root cause of the problem is that the Provider registered the
> > > method.async to the registry and finally affected the Consumer side.
> > >
> > > The user submitted pr[2] to fix the problem. The fix is that the provider
> > > does not register the method.async to the registry, so the Consumer side
> > > cannot perceive it.
> > > I think this way is not the best. I think the best way is that the
> > Provider
> > > side still registers method.async to the registry, but the Consumer side
> > > ignores this property.
> >
> > Do you have any idea how to achieve this? Do we need to have extra
> > configuration on consumer side?
> > Or is it a special case?
> >
> > > The advantage is that in the future we can still see
> > > the asynchronous situation of the various methods of the provider on
> > > dubbo-ops,
> >
> > +1
> >
> > > and this processing method is more in line with the purpose of
> > > dubbo configuration coverage.
> > >
> > > What do you think about it?
> > >
> > > [1]https://github.com/apache/incubator-dubbo/issues/2321
> > > [2]https://github.com/apache/incubator-dubbo/pull/2322
> >
> > I also noticed that you have replied on the issue:
> >
> > > When using , the Consumer will not be
> > affected. However, the Consumer call will be affected when using
> > .
> >
> > Why they are not consistent?
> >
> > --
> > Best Regards！
> > Huxing
> >



-- 
Best Regards！
Huxing

Re: about grpc support

[Jerrick Zhu]

Actually this task doesn't start yet.

U are welcome if u could join to start it.

On Wed, Sep 12, 2018 at 11:16 AM 莫里亚提 <1249499...@qq.com> wrote:

> hello:
>
>
>   想了解下dubbo grpc协议支持feature的进展。我的理解，要支持grpc streaming调用的特性的话，需要使用grpc stub
> layer，但是在export， refer， invoker这些grpc组件对接
>
>
> 的设计上有些疑惑。有人正在做相应的事情吗？
>
>
>
>
> Best Regards,
> dp

Re: [ANNOUNCE] Welcome new committer Minxuan Zhuang

[Huxing Zhang]

Congratulations!
On Tue, Sep 11, 2018 at 8:39 PM Jun Liu  wrote:
>
> Hi, Community,
>
> On behalf of the Dubbo PPMC, I am pleased to announce that Minxuan Zhuang, 
> whose github id is nzomkxia, has been voted in as a new Dubbo committer.
>
> He has did and is doing a great job on dubbo-ops, and I just want to say 
> thanks and congratulations. Please join me to say congratulations to Minxuan!
>
> Minxuan, would you please briefly introduce yourself to the community?
>
> Best regards,
> Jun
>


-- 
Best Regards！
Huxing

Re: [ANNOUNCE] 2.6.3 has been released.

[Huxing Zhang]

On Wed, Sep 12, 2018 at 8:48 AM jun liu  wrote:
>
> Huxing,
>
> > Source release:
> > https://www.apache.org/dyn/closer.cgi?path=incubator/dubbo/2.6.3/apache-dubbo-incubating-2.6.3-source-release.zip
> > Binary release:
> > https://www.apache.org/dyn/closer.cgi?path=incubator/dubbo/2.6.3/apache-dubbo-incubating-2.6.3-bin-release
> >  
> > 
> Where are we going to add this links?

The links should be added to the official website, maybe we should
have dedicated page [1] for the download information.

And the documentation need to be updated, for example in [2], instead
of clone from Github, guide user to use the latest stable release. (Of
course for cutting edge users, Github clone is still available)

[1] 
http://commons.apache.org/proper/commons-collections/download_collections.cgi
[2] http://dubbo.apache.org/en-us/docs/admin/install/provider-demo.html

>
> Best regards,
> Jun
>
> > On 12 Sep 2018, at 07:34, Huxing Zhang  wrote:
> >
> > Glad to hear that!
> >
> > There is one more thing to do: add download link to the official ASF 
> > release.
> >
> > Source release:
> > https://www.apache.org/dyn/closer.cgi?path=incubator/dubbo/2.6.3/apache-dubbo-incubating-2.6.3-source-release.zip
> > Binary release:
> > https://www.apache.org/dyn/closer.cgi?path=incubator/dubbo/2.6.3/apache-dubbo-incubating-2.6.3-bin-release.zip
> >
> > On Tue, Sep 11, 2018 at 8:10 PM Jun Liu  wrote:
> >>
> >> Hi Community,
> >>
> >> I am pleased to announce that the 2.6.3 version has just been released. 
> >> Both the source release[1] and the maven binary release[2] are available 
> >> now, you can also find the detailed release notes in here[3] or quickly 
> >> check the important changes I list below:
> >> * Delivery of attachments from provider to consumer.
> >> * Generic invoke and attachments for http protocol.
> >> * Introduce new bootstrap module
> >> * Performance tuning
> >> * Bugfixes
> >>
> >> Normally, you can smoothly upgrade to the new version from any version 
> >> before 2.6.2 without having to do too many changes to your apps and 
> >> without having to worry about any incompatible problems.
> >> If you have any usage questions, or have problems when upgrading or find 
> >> any problems about enhancements included in this release, please don’t 
> >> hesitate to let us know by sending feedback to this mailing list or filing 
> >> an issue on github[4].
> >>
> >> 1. https://dist.apache.org/repos/dist/release/incubator/dubbo/2.6.3/
> >> 2. http://central.maven.org/maven2/com/alibaba/
> >> 3. https://github.com/apache/incubator-dubbo/releases
> >> 4. https://github.com/apache/incubator-dubbo/issues
> >>
> >> Best regards,
> >> Jun
> >>
> >
> >
> > --
> > Best Regards！
> > Huxing
>


-- 
Best Regards！
Huxing

Re: [Discuss]Prepare for the next release v2.6.4

[Huxing Zhang]

On Mon, Sep 10, 2018 at 10:35 AM Jun Liu  wrote:
>
> > Do you think we need another one to be the release manager? In case
> > that we can make sure our release guide works perfectly.
>
> Yes, I think we need a new manager to do the next release, to get familiar 
> with and improve the release process.

Is anyone who volunteers to be the release manager?

> But I'm not sure if anyone has committer privilege is allowed to be the 
> release manager or only PMCs are allowed.

I checked the release policy [1], it seems no requirement for non-PMC
member to be release manager.

> If the Release Manager is not a member of the PMC, they will need to ask a 
> PMC member to do the actual release publication.


[1] http://www.apache.org/legal/release-policy.html#upload-ci

>
> Best regards,
> Jun
>
> > On 7 Sep 2018, at 23:42, Huxing Zhang  wrote:
> >
> > Hi,
> >
> > On Sat, Sep 1, 2018 at 4:18 PM Jun Liu  wrote:
> >>
> >> Hi, Community,
> >>
> >> I think it’s time to start preparing for the release of the 2.6.4 version 
> >> now. The vote of v2.6.3 has lasted for nearly a month and we can expect it 
> >> to be released in the next two weeks if it can pass the Apache community 
> >> vote later. During such a relatively long period of time, I have seen some 
> >> important patches being merged into branch 2.6.x[1], some issues need to 
> >> be fixed most of which are collected from users/developers in community 
> >> are included in milestone 2.6.4[2].
> >>
> >> Counting the time needed to address all these issues and the time we have 
> >> to wait for the voting, let's speed up the progress of v2.6.4.
> >
> > Do you think we need another one to be the release manager? In case
> > that we can make sure our release guide works perfectly.
> >
> >>
> >> Best regards,
> >> Jun
> >>
> >
> >
> > --
> > Best Regards！
> > Huxing
>


-- 
Best Regards！
Huxing

Issue all of the random failed UT cases

[Jerrick Zhu]

Hi, community

I found that many cases failed on travis, randomly.

https://github.com/apache/incubator-dubbo/issues/2492
https://github.com/apache/incubator-dubbo/issues/2490
https://github.com/apache/incubator-dubbo/issues/2484
https://github.com/apache/incubator-dubbo/issues/2482
https://github.com/apache/incubator-dubbo/issues/2462

But when rebuild them, it's ok.

So I suggest that issue all of the failed cases, so that the
community can check it out later.

Re: Local forced trigger mock does not take effect

[Ian Luo]

Jun,

Are you suggesting the mock behavior works as expected? If so, we may
consider to add the corresponding samples if we have done it yet.

Thanks,
-Ian.


On Wed, Sep 12, 2018 at 8:56 AM jun liu  wrote:

> >  > interface="com.alibaba.dubbo.samples.mock.api.DemoService" mock="force”/>
>
> As far as I can describe now, I think you can use:
> 1. mock=“true”, this will direct the to the default mock implementation
> with a name convention like DemoServiceMock.
> 2. mock=“force:return xxx”, directly specify the return value you want.
> This may be the case you want to use, but I think you just forget the mock
> value you want.
> 3. mock=“org.apache.dubbo.xxx.xxxMock”, specify the class where your mock
> logic is located.
>
> > `com.alibaba.dubbo.common.utils.ConfigUtils#isDefault` should support
> > force? Can someone help me?
>
> Given the above usage supported I think there’s no need to add an extra
> mock=“force” support. What do u think?
>
> Best regards,
> Jun
>
> > On 11 Sep 2018, at 16:31, Zonghai Shang  wrote:
> >
> > Hi,
> >
> > MockClusterInvoker provides local forced mock，I tested it locally, but it
> > doesn't work.
> >
> > @Override
> > public Result invoke(Invocation invocation) throws RpcException {
> >// ….
> >else if (value.startsWith("force")) {
> >if (logger.isWarnEnabled()) {
> >logger.info("force-mock: " + invocation.getMethodName() + "
> > force-mock enabled , url : " + directory.getUrl());
> >}
> >//force:direct mock
> >result = doMockInvoke(invocation, null);
> >}
> >   // ….
> > }
> >
> >  > interface="com.alibaba.dubbo.samples.mock.api.DemoService" mock="force”/>
> >
> > Here is demo:
> > https://github.com/dubbo/dubbo-samples/tree/master/dubbo-samples-mock
> >
> > `com.alibaba.dubbo.common.utils.ConfigUtils#isDefault` should support
> > force? Can someone help me?
> >
> > yiji
>
>

Re: [ANNOUNCE] 2.6.3 has been released.

[Huxing Zhang]

Glad to hear that!

There is one more thing to do: add download link to the official ASF release.

Source release:
https://www.apache.org/dyn/closer.cgi?path=incubator/dubbo/2.6.3/apache-dubbo-incubating-2.6.3-source-release.zip
Binary release:
https://www.apache.org/dyn/closer.cgi?path=incubator/dubbo/2.6.3/apache-dubbo-incubating-2.6.3-bin-release.zip

On Tue, Sep 11, 2018 at 8:10 PM Jun Liu  wrote:
>
> Hi Community,
>
> I am pleased to announce that the 2.6.3 version has just been released. Both 
> the source release[1] and the maven binary release[2] are available now, you 
> can also find the detailed release notes in here[3] or quickly check the 
> important changes I list below:
> * Delivery of attachments from provider to consumer.
> * Generic invoke and attachments for http protocol.
> * Introduce new bootstrap module
> * Performance tuning
> * Bugfixes
>
> Normally, you can smoothly upgrade to the new version from any version before 
> 2.6.2 without having to do too many changes to your apps and without having 
> to worry about any incompatible problems.
> If you have any usage questions, or have problems when upgrading or find any 
> problems about enhancements included in this release, please don’t hesitate 
> to let us know by sending feedback to this mailing list or filing an issue on 
> github[4].
>
> 1. https://dist.apache.org/repos/dist/release/incubator/dubbo/2.6.3/
> 2. http://central.maven.org/maven2/com/alibaba/
> 3. https://github.com/apache/incubator-dubbo/releases
> 4. https://github.com/apache/incubator-dubbo/issues
>
> Best regards,
> Jun
>


-- 
Best Regards！
Huxing

Re: Local forced trigger mock does not take effect

[Ian Luo]

I did a quick check in samples project, and it did have samples to
demonstrate mock functionality. Pls. ignore my last email.

On Wed, Sep 12, 2018 at 10:19 AM Ian Luo  wrote:

> Jun,
>
> Are you suggesting the mock behavior works as expected? If so, we may
> consider to add the corresponding samples if we have done it yet.
>
> Thanks,
> -Ian.
>
>
> On Wed, Sep 12, 2018 at 8:56 AM jun liu  wrote:
>
>> > > > interface="com.alibaba.dubbo.samples.mock.api.DemoService"
>> mock="force”/>
>>
>> As far as I can describe now, I think you can use:
>> 1. mock=“true”, this will direct the to the default mock implementation
>> with a name convention like DemoServiceMock.
>> 2. mock=“force:return xxx”, directly specify the return value you want.
>> This may be the case you want to use, but I think you just forget the mock
>> value you want.
>> 3. mock=“org.apache.dubbo.xxx.xxxMock”, specify the class where your mock
>> logic is located.
>>
>> > `com.alibaba.dubbo.common.utils.ConfigUtils#isDefault` should support
>> > force? Can someone help me?
>>
>> Given the above usage supported I think there’s no need to add an extra
>> mock=“force” support. What do u think?
>>
>> Best regards,
>> Jun
>>
>> > On 11 Sep 2018, at 16:31, Zonghai Shang  wrote:
>> >
>> > Hi,
>> >
>> > MockClusterInvoker provides local forced mock，I tested it locally, but
>> it
>> > doesn't work.
>> >
>> > @Override
>> > public Result invoke(Invocation invocation) throws RpcException {
>> >// ….
>> >else if (value.startsWith("force")) {
>> >if (logger.isWarnEnabled()) {
>> >logger.info("force-mock: " + invocation.getMethodName() + "
>> > force-mock enabled , url : " + directory.getUrl());
>> >}
>> >//force:direct mock
>> >result = doMockInvoke(invocation, null);
>> >}
>> >   // ….
>> > }
>> >
>> > > > interface="com.alibaba.dubbo.samples.mock.api.DemoService"
>> mock="force”/>
>> >
>> > Here is demo:
>> > https://github.com/dubbo/dubbo-samples/tree/master/dubbo-samples-mock
>> >
>> > `com.alibaba.dubbo.common.utils.ConfigUtils#isDefault` should support
>> > force? Can someone help me?
>> >
>> > yiji
>>
>>

Re: Local forced trigger mock does not take effect

[yuhang xiu]

Hi guys,

I also encountered this confusion when I configured the mock in xml.
Now it seems that the form of mock=force:return xxx can only be used when
dynamically configured using the override protocol, which does not match
the configuration of the xml.

I think we need to do one of the following two things:
1. Improve the documentation
2. Consider the configuration of xml compatible with the configuration of
the override protocol

Zonghai Shang  于2018年9月12日周三 上午10:24写道：

> > 1. mock=“true”, this will direct the to the default mock implementation
> with a name convention like DemoServiceMock.
> > 3. mock=“org.apache.dubbo.xxx.xxxMock”, specify the class where your mock
> logic is located.
>
> mock=“org.apache.dubbo.xxx.xxxMock” , only throw RpcException to execute
> the mock, which does not match the force logic.
>
> > 2. mock=“force:return xxx”, directly specify the return value you want.
> This may be the case you want to use, but I think you just forget the mock
> value you want.
>
> It does’t work, cause:
> PropertyAccessException 1:
> org.springframework.beans.MethodInvocationException: Property 'mock' threw
> exception; nested exception is java.lang.IllegalStateException: Invalid
> mock="force:return null" contain illegal charactor, only digit, letter,
> '-', '_' and '.' is legal.
>
> I think maybe the implementation of mock may have bugs.
>
>
> Best regards,
> yiji
>
> jun liu  于2018年9月12日周三 上午8:56写道：
>
> > >  > > interface="com.alibaba.dubbo.samples.mock.api.DemoService"
> mock="force”/>
> >
> > As far as I can describe now, I think you can use:
> > 1. mock=“true”, this will direct the to the default mock implementation
> > with a name convention like DemoServiceMock.
> > 2. mock=“force:return xxx”, directly specify the return value you want.
> > This may be the case you want to use, but I think you just forget the
> mock
> > value you want.
> > 3. mock=“org.apache.dubbo.xxx.xxxMock”, specify the class where your mock
> > logic is located.
> >
> > > `com.alibaba.dubbo.common.utils.ConfigUtils#isDefault` should support
> > > force? Can someone help me?
> >
> > Given the above usage supported I think there’s no need to add an extra
> > mock=“force” support. What do u think?
> >
> > Best regards,
> > Jun
> >
> > > On 11 Sep 2018, at 16:31, Zonghai Shang  wrote:
> > >
> > > Hi,
> > >
> > > MockClusterInvoker provides local forced mock，I tested it locally, but
> it
> > > doesn't work.
> > >
> > > @Override
> > > public Result invoke(Invocation invocation) throws RpcException {
> > >// ….
> > >else if (value.startsWith("force")) {
> > >if (logger.isWarnEnabled()) {
> > >logger.info("force-mock: " + invocation.getMethodName() + "
> > > force-mock enabled , url : " + directory.getUrl());
> > >}
> > >//force:direct mock
> > >result = doMockInvoke(invocation, null);
> > >}
> > >   // ….
> > > }
> > >
> > >  > > interface="com.alibaba.dubbo.samples.mock.api.DemoService"
> mock="force”/>
> > >
> > > Here is demo:
> > > https://github.com/dubbo/dubbo-samples/tree/master/dubbo-samples-mock
> > >
> > > `com.alibaba.dubbo.common.utils.ConfigUtils#isDefault` should support
> > > force? Can someone help me?
> > >
> > > yiji
> >
> >
>

关于dubbo的版本

[宗荣]

http://mvnrepository.com/artifact/com.alibaba/dubbo这个是dubbo版本的官方地址吗，里面的最新版本是2.6.3，但我看网上有一些版本已经到了2.8.4，我是一名刚开始学习dubbo的开发人员，不知能否帮忙解答下，谢谢！

Re: 关于dubbo的版本

[Jerrick Zhu]

The newest version is 2.6.3. U can use this.

2.8.x is the dubbox, forked by dangdang.com. But now it has been
deprecated, the main feature(rest) has been merged back to dubbo. Do not
use dubbox again.

On Wed, Sep 12, 2018 at 11:06 AM 宗荣  wrote:

> http://mvnrepository.com/artifact/com.alibaba/dubbo
> 这个是dubbo版本的官方地址吗，里面的最新版本是2.6.3，但我看网上有一些版本已经到了2.8.4，我是一名刚开始学习dubbo的开发人员，不知能否帮忙解答下，谢谢！

[DISCUSS] A metric to measure the response time to issues/prs

[Huxing Zhang]

Hi,

I just find an article [1] complaining about the response time to pull
request and issues.

I think we can use a metric to measure the response time, and I found this [2].

It looks like we are not doing very well.

Does the community think it is useful to have such an metric?

Is there anything we can do to improve it?

[1] https://paper.tuisec.win/detail/0990f6a290f042e
[2] https://isitmaintained.com/project/apache/incubator-dubbo

-- 
Best Regards！
Huxing

Re: Travis CI failed

[Ian Luo]

I suggest to add back maven cache configuration to check if it's recovered.
It helps on speeding the build.

On Wed, Sep 12, 2018 at 8:47 AM Jerrick Zhu  wrote:

> When I enabled -X, I didn't get any useful informations. Neither upgrading
> maven-compile-plugin.
> After that I wanted to remove it in .m2, so removing the cache
> configuration.
>
> Until now I do not find out the reason.
>
> On Wed, Sep 12, 2018 at 7:37 AM Huxing Zhang  wrote:
>
> > Hi,
> >
> > On Tue, Sep 11, 2018 at 11:41 AM Jerrick Zhu  wrote:
> > >
> > > I try to remove the cache in .travis.yml,
> > >
> > > ```
> > > cache:
> > > directories:
> > > - '$HOME/.m2/repository'
> > > ```
> >
> > I have also tried a few times. How did you find it out? Are you using
> > maven -X for debugging?
> >
> > >
> > > Now it works. Maybe the cache affects the build process.
> > >
> > > I'll file a PR on master.
> > >
> > > On Mon, Sep 10, 2018 at 4:57 PM Jerrick Zhu 
> wrote:
> > >
> > > > I tried to restart the build for a few times, it failed with the same
> > > > error.
> > > >
> > > > On Mon, Sep 10, 2018 at 1:56 PM yuhang xiu 
> wrote:
> > > >
> > > >> Hi,
> > > >> I also checked the log just now and found no problems. I have
> > restarted
> > > >> this task, I will observe the results after a while.
> > > >>
> > > >> YunKun Huang  于2018年9月10日周一 下午1:53写道：
> > > >>
> > > >> > Check this log, it says compile fail on dubbo-common module:
> > > >> > https://travis-ci.org/apache/incubator-dubbo/jobs/426109384
> > > >> >
> > > >> > But there is no code change since latest successful bulid.
> > > >> > Also I try to run build in my local, it pass with jdk 8.
> > > >> >
> > > >> > On 2018/09/10 05:36:27, Jerrick Zhu  wrote:
> > > >> > > Hi, community
> > > >> > >
> > > >> > > I found that all travis CI builds failed on Java8.
> > > >> > >
> > > >> > > Here is the master's build:
> > > >> https://travis-ci.org/apache/incubator-dubbo
> > > >> > >
> > > >> > > Anyone can help to check it?
> > > >> > >
> > > >> >
> > > >>
> > > >
> >
> >
> >
> > --
> > Best Regards！
> > Huxing
> >
>

Re: [DISCUSS] A metric to measure the response time to issues/prs

[yuhang xiu]

Hi,

Maintaining dubbo is not the main job of many people, so there may be a
delay in processing the pr.

In addition, I have a pr that has been placed for more than 30 days, but I
don't want it to be merged as soon as possible, but I hope it will be
reviewed and recognized by more people.

As long as the quality is guaranteed, it can be processed as soon as
possible. This is my point of view.

Best regards!

Huxing Zhang  于2018年9月12日周三 下午4:33写道：

> Hi,
>
> On Wed, Sep 12, 2018 at 4:12 PM kirito  wrote:
> >
> > Hi
> >
> > With this topic, I ask a question. Look me as normal dubbo user
> >
> > What’s more can I do to speed up the merge of these pr? A mail to the
> mailing list? @ the member?
>
> I would suggest review the existing prs and leave your feedback, any
> comments is welcome, if you feel it looks good. Just comment "Looks
> good to me or LGTM".
>
> >
> > Like this  pull request,
> https://github.com/apache/incubator-dubbo/pull/2418 <
> https://github.com/apache/incubator-dubbo/pull/2418> . Its changes maybe
> very small to fix a bug of dubbo, maybe we can merge these more quickly .
> >
> > xujingfeng
> >
> >
> 
>
>
> --
> Best Regards！
> Huxing
>

[Dubbo benchmark ]The test results are mixed with the dubbo log.

[Zonghai Shang]

Hi ,

I am using performance testing to find out that the output is confusing, it
would be better if the output is supported to the file.
dubbo-benchmark: https://github.com/dubbo/dubbo-benchmark
Here is my test output:

```
# Fork: 1 of 1
# Warmup Iteration   1: Sep 12, 2018 2:22:31 PM
org.springframework.context.support.ClassPathXmlApplicationContext
prepareRefresh
信息: Refreshing
org.springframework.context.support.ClassPathXmlApplicationContext@44dc6a41:
startup date [Wed Sep 12 14:22:31 CST 2018]; root of context hierarchy
Sep 12, 2018 2:22:31 PM
org.springframework.beans.factory.xml.XmlBeanDefinitionReader
loadBeanDefinitions
信息: Loading XML bean definitions from class path resource [consumer.xml]
14:22:31.775 [org.apache.dubbo.benchmark.Client.listUser-jmh-worker-1] INFO
 c.a.d.common.logger.LoggerFactory - using logger:
com.alibaba.dubbo.common.logger.slf4j.Slf4jLoggerAdapter
14:22:32.040 [org.apache.dubbo.benchmark.Client.listUser-jmh-worker-1] INFO
 c.a.d.r.protocol.dubbo.DubboProtocol -  [DUBBO] Optimizing the
serialization process for Kryo, FST, etc..., dubbo version: 2.6.1, current
host: 172.17.9.71
2.841 ±(99.9%) 0.015 ms/op
# Warmup Iteration   2: 2.464 ±(99.9%) 0.010 ms/op
# Warmup Iteration   3: 2.541 ±(99.9%) 0.007 ms/op
Iteration   1: 2.342 ±(99.9%) 0.005 ms/op
 listUser·p0.00:   0.785 ms/op
```

Thanks
yiji

Re: [DISCUSS] A metric to measure the response time to issues/prs

[Ian Luo]

Let's do it in simple way. Pls. put 'issue resolution' and 'open issues'
icons straightforward on the head of the README.md.

Let's face it and don't be shame.

On Wed, Sep 12, 2018 at 3:44 PM Jerrick Zhu  wrote:

> On Wed, Sep 12, 2018 at 12:53 PM Huxing Zhang  wrote:
>
> > Hi,
> >
> > I just find an article [1] complaining about the response time to pull
> > request and issues.
> >
>
> That's true. Our issue/PR's response time is too long.
>
>
> >
> > I think we can use a metric to measure the response time, and I found
> this
> > [2].
> >
> > It looks like we are not doing very well.
> >
> > Does the community think it is useful to have such an metric?
> >
>
> A metric is just a way but not a solution.
>
> Actually we need to call for the whole community to join, respond to
> issues, review PRs. But this must start from the PPMC and committers.
>
>
> >
> > Is there anything we can do to improve it?
> >
> > [1] https://paper.tuisec.win/detail/0990f6a290f042e
> > [2] https://isitmaintained.com/project/apache/incubator-dubbo
> >
> > --
> > Best Regards！
> > Huxing
> >
>

Re: 关于dubbo的版本

[Huxing Zhang]

Hi,

There is an FAQ item related to this:
https://github.com/apache/incubator-dubbo/blob/master/FAQ.md#which-version-should-i-choose


On Wed, Sep 12, 2018 at 11:06 AM 宗荣  wrote:
>
> http://mvnrepository.com/artifact/com.alibaba/dubbo这个是dubbo版本的官方地址吗，里面的最新版本是2.6.3，但我看网上有一些版本已经到了2.8.4，我是一名刚开始学习dubbo的开发人员，不知能否帮忙解答下，谢谢！



-- 
Best Regards！
Huxing

Re: about grpc support

[Jason Joo]

hi, dp

According to principle of gRPC which is a solution crossing front-end(mobile) 
to back-end(server) using HTTP/2, i think it's suitable to be integrated in 
Controller layer(some like dubbo-consumer) but not service 
layer(dubbo-provider).

Nothing blocks us to use gRPC in consumers, right?


gRPC是一个跨端整体调用解决方案，这个个人理解一般应用在业务逻辑层，也就是一般对应dubbo的消费端，而不是服务端，所以两者完全可以融合使用，如下：

mobile <---gRPC> controller <-dubbo-> service <> ...

不知道这个跟你想的是否一致？


best regards,

Jason

> On Sep 12, 2018, at 11:16, 莫里亚提 <1249499...@qq.com> wrote:
> 
> hello:
> 
> 
>  想了解下dubbo grpc协议支持feature的进展。我的理解，要支持grpc streaming调用的特性的话，需要使用grpc stub 
> layer，但是在export， refer， invoker这些grpc组件对接
> 
> 
> 的设计上有些疑惑。有人正在做相应的事情吗？
> 
> 
> 
> 
> Best Regards,
> dp

Re: Local forced trigger mock does not take effect

[Ian Luo]

Jingfeng,

Further more, is there a need to provide support for
> `fail:`,`force:`,`throw`? What the behavior they should own?
>

I think 'fail:', 'force:' should work, pls. check the code here [1]. What
unexpected behavior did you see? I have not tried it out, but it looks we
have the corresponding support but don't have it described in the doc.

1.
https://github.com/apache/incubator-dubbo/blob/master/dubbo-cluster/src/main/java/org/apache/dubbo/rpc/cluster/support/wrapper/MockClusterInvoker.java#L76

On Wed, Sep 12, 2018 at 2:47 PM kirito  wrote:

> Hi
>
> I have a try right now,it was very strange.
>  interface="com.alibaba.dubbo.samples.mock.api.DemoService" mock="return
> null"/>
> Works very well, but I think the blank is a illegal character too.
> As exception says :
>
> > invalid mock=“" contain illegal character, only digit, letter, '-',
> '_' and '.' is legal.
>
>
> And I search for the dubbo source code find that in
> `com.alibaba.dubbo.common.Constants` exist below attributes
>
> public static final String MOCK_PROTOCOL = "mock";
> public static final String RETURN_PREFIX = "return ";
> public static final String THROW_PREFIX = "throw";
> public static final String FAIL_PREFIX = "fail:";
> public static final String FORCE_PREFIX = "force:";
> public static final String FORCE_KEY = "force”;
>
> While search for the doc
> https://dubbo.apache.org/zh-cn/docs/user/demos/local-mock.html, <
> https://dubbo.apache.org/zh-cn/docs/user/demos/local-mock.html,it> it
> looks like that dubbo doesn’t support throw,fail,force. Maybe any of these
> attributes are internal?
>
> I think the subject submitted by @yiji was a limitation of spring xml
> parser. The character ‘:’ need treated specially.
> Further more, is there a need to provide support for
> `fail:`,`force:`,`throw`? What the behavior they should own?
> As I know,these way works very well now
> > 1. mock=“true”, this will direct the to the default mock implementation
> > 2. mock=“return null”
> > 3. mock=“org.apache.dubbo.xxx.xxxMock”, specify the class where your mock
>
> What do you think about this? It will help us to review the further
> changes.
>
> xujingfeng
>
> > 在 2018年9月12日，下午1:52，Zonghai Shang  写道：
> >
> > I have found it , I will fix it later.
> >
> > yiji
> >
> > jun liu  于2018年9月12日周三 下午12:45写道：
> >
> >>
>  2. mock=“force:return xxx”, directly specify the return value you
> want.
> >>> This may be the case you want to use, but I think you just forget the
> >> mock
> >>> value you want.
> >>>
> >>> It does’t work, cause:
> >>> PropertyAccessException 1:
> >>> org.springframework.beans.MethodInvocationException: Property 'mock'
> >> threw
> >>> exception; nested exception is java.lang.IllegalStateException: Invalid
> >>> mock="force:return null" contain illegal charactor, only digit, letter,
> >>> '-', '_' and '.' is legal.
> >>>
> >>> I think maybe the implementation of mock may have bugs.
> >>
> >> I haven’t tried this usage in xml yet, seems like we need to find the
> >> problem and fix it so that it can work properly as expected.
> >>
> >> Best regards,
> >> Jun
> >>
> >>> On 12 Sep 2018, at 10:24, Zonghai Shang  wrote:
> >>>
>  1. mock=“true”, this will direct the to the default mock
> implementation
> >>> with a name convention like DemoServiceMock.
>  3. mock=“org.apache.dubbo.xxx.xxxMock”, specify the class where your
> >> mock
> >>> logic is located.
> >>>
> >>> mock=“org.apache.dubbo.xxx.xxxMock” , only throw RpcException to
> execute
> >>> the mock, which does not match the force logic.
> >>>
>  2. mock=“force:return xxx”, directly specify the return value you
> want.
> >>> This may be the case you want to use, but I think you just forget the
> >> mock
> >>> value you want.
> >>>
> >>> It does’t work, cause:
> >>> PropertyAccessException 1:
> >>> org.springframework.beans.MethodInvocationException: Property 'mock'
> >> threw
> >>> exception; nested exception is java.lang.IllegalStateException: Invalid
> >>> mock="force:return null" contain illegal charactor, only digit, letter,
> >>> '-', '_' and '.' is legal.
> >>>
> >>> I think maybe the implementation of mock may have bugs.
> >>>
> >>>
> >>> Best regards,
> >>> yiji
> >>>
> >>> jun liu  于2018年9月12日周三 上午8:56写道：
> >>>
> >  > interface="com.alibaba.dubbo.samples.mock.api.DemoService"
> >> mock="force”/>
> 
>  As far as I can describe now, I think you can use:
>  1. mock=“true”, this will direct the to the default mock
> implementation
>  with a name convention like DemoServiceMock.
>  2. mock=“force:return xxx”, directly specify the return value you
> want.
>  This may be the case you want to use, but I think you just forget the
> >> mock
>  value you want.
>  3. mock=“org.apache.dubbo.xxx.xxxMock”, specify the class where your
> >> mock
>  logic is located.
> 
> > `com.alibaba.dubbo.common.utils.ConfigUtils#isDefault` should support
> > force? Can someone help me?
> 
>  Given the above usage 

Re: Local forced trigger mock does not take effect

[kirito]

Hi

I have a try right now,it was very strange.

Works very well, but I think the blank is a illegal character too. 
As exception says : 

> invalid mock=“" contain illegal character, only digit, letter, '-', '_' 
> and '.' is legal.


And I search for the dubbo source code find that in 
`com.alibaba.dubbo.common.Constants` exist below attributes

public static final String MOCK_PROTOCOL = "mock";
public static final String RETURN_PREFIX = "return ";
public static final String THROW_PREFIX = "throw";
public static final String FAIL_PREFIX = "fail:";
public static final String FORCE_PREFIX = "force:";
public static final String FORCE_KEY = "force”;

While search for the doc 
https://dubbo.apache.org/zh-cn/docs/user/demos/local-mock.html, 
 it looks 
like that dubbo doesn’t support throw,fail,force. Maybe any of these attributes 
are internal?  

I think the subject submitted by @yiji was a limitation of spring xml parser. 
The character ‘:’ need treated specially. 
Further more, is there a need to provide support for `fail:`,`force:`,`throw`? 
What the behavior they should own? 
As I know,these way works very well now
> 1. mock=“true”, this will direct the to the default mock implementation
> 2. mock=“return null”
> 3. mock=“org.apache.dubbo.xxx.xxxMock”, specify the class where your mock

What do you think about this? It will help us to review the further changes.

xujingfeng

> 在 2018年9月12日，下午1:52，Zonghai Shang  写道：
> 
> I have found it , I will fix it later.
> 
> yiji
> 
> jun liu  于2018年9月12日周三 下午12:45写道：
> 
>> 
 2. mock=“force:return xxx”, directly specify the return value you want.
>>> This may be the case you want to use, but I think you just forget the
>> mock
>>> value you want.
>>> 
>>> It does’t work, cause:
>>> PropertyAccessException 1:
>>> org.springframework.beans.MethodInvocationException: Property 'mock'
>> threw
>>> exception; nested exception is java.lang.IllegalStateException: Invalid
>>> mock="force:return null" contain illegal charactor, only digit, letter,
>>> '-', '_' and '.' is legal.
>>> 
>>> I think maybe the implementation of mock may have bugs.
>> 
>> I haven’t tried this usage in xml yet, seems like we need to find the
>> problem and fix it so that it can work properly as expected.
>> 
>> Best regards,
>> Jun
>> 
>>> On 12 Sep 2018, at 10:24, Zonghai Shang  wrote:
>>> 
 1. mock=“true”, this will direct the to the default mock implementation
>>> with a name convention like DemoServiceMock.
 3. mock=“org.apache.dubbo.xxx.xxxMock”, specify the class where your
>> mock
>>> logic is located.
>>> 
>>> mock=“org.apache.dubbo.xxx.xxxMock” , only throw RpcException to execute
>>> the mock, which does not match the force logic.
>>> 
 2. mock=“force:return xxx”, directly specify the return value you want.
>>> This may be the case you want to use, but I think you just forget the
>> mock
>>> value you want.
>>> 
>>> It does’t work, cause:
>>> PropertyAccessException 1:
>>> org.springframework.beans.MethodInvocationException: Property 'mock'
>> threw
>>> exception; nested exception is java.lang.IllegalStateException: Invalid
>>> mock="force:return null" contain illegal charactor, only digit, letter,
>>> '-', '_' and '.' is legal.
>>> 
>>> I think maybe the implementation of mock may have bugs.
>>> 
>>> 
>>> Best regards,
>>> yiji
>>> 
>>> jun liu  于2018年9月12日周三 上午8:56写道：
>>> 
>  interface="com.alibaba.dubbo.samples.mock.api.DemoService"
>> mock="force”/>
 
 As far as I can describe now, I think you can use:
 1. mock=“true”, this will direct the to the default mock implementation
 with a name convention like DemoServiceMock.
 2. mock=“force:return xxx”, directly specify the return value you want.
 This may be the case you want to use, but I think you just forget the
>> mock
 value you want.
 3. mock=“org.apache.dubbo.xxx.xxxMock”, specify the class where your
>> mock
 logic is located.
 
> `com.alibaba.dubbo.common.utils.ConfigUtils#isDefault` should support
> force? Can someone help me?
 
 Given the above usage supported I think there’s no need to add an extra
 mock=“force” support. What do u think?
 
 Best regards,
 Jun
 
> On 11 Sep 2018, at 16:31, Zonghai Shang  wrote:
> 
> Hi,
> 
> MockClusterInvoker provides local forced mock，I tested it locally, but
>> it
> doesn't work.
> 
> @Override
> public Result invoke(Invocation invocation) throws RpcException {
>  // ….
>  else if (value.startsWith("force")) {
>  if (logger.isWarnEnabled()) {
>  logger.info("force-mock: " + invocation.getMethodName() + "
> force-mock enabled , url : " + directory.getUrl());
>  }
>  //force:direct mock
>  result = doMockInvoke(invocation, null);
>  }
> // ….
> }
> 
>  interface="com.alibaba.dubbo.samples.mock.api.DemoService"

Re: [DISCUSS] A metric to measure the response time to issues/prs

[kirito]

Hi

With this topic, I ask a question. Look me as normal dubbo user

What’s more can I do to speed up the merge of these pr? A mail to the mailing 
list? @ the member?

Like this  pull request, https://github.com/apache/incubator-dubbo/pull/2418 
 . Its changes maybe very 
small to fix a bug of dubbo, maybe we can merge these more quickly .

xujingfeng


> 在 2018年9月12日，下午3:55，Ian Luo  写道：
> 
> Let's do it in simple way. Pls. put 'issue resolution' and 'open issues'
> icons straightforward on the head of the README.md.
> 
> Let's face it and don't be shame.
> 
> On Wed, Sep 12, 2018 at 3:44 PM Jerrick Zhu  wrote:
> 
>> On Wed, Sep 12, 2018 at 12:53 PM Huxing Zhang  wrote:
>> 
>>> Hi,
>>> 
>>> I just find an article [1] complaining about the response time to pull
>>> request and issues.
>>> 
>> 
>> That's true. Our issue/PR's response time is too long.
>> 
>> 
>>> 
>>> I think we can use a metric to measure the response time, and I found
>> this
>>> [2].
>>> 
>>> It looks like we are not doing very well.
>>> 
>>> Does the community think it is useful to have such an metric?
>>> 
>> 
>> A metric is just a way but not a solution.
>> 
>> Actually we need to call for the whole community to join, respond to
>> issues, review PRs. But this must start from the PPMC and committers.
>> 
>> 
>>> 
>>> Is there anything we can do to improve it?
>>> 
>>> [1] https://paper.tuisec.win/detail/0990f6a290f042e
>>> [2] https://isitmaintained.com/project/apache/incubator-dubbo
>>> 
>>> --
>>> Best Regards！
>>> Huxing
>>> 
>> 

Re: [ANNOUNCE] Welcome new committer Minxuan Zhuang

[Jerrick Zhu]

Congrats.

On Wed, Sep 12, 2018 at 11:44 AM Zonghai Shang  wrote:

> Congratulations!
>
> yiji
>
> yuhang xiu  于2018年9月12日周三 上午10:09写道：
>
> > Congratulations!
> > Welcome to Dubbo. :)
> >
> > Huxing Zhang  于2018年9月12日周三 上午7:26写道：
> >
> > > Congratulations!
> > > On Tue, Sep 11, 2018 at 8:39 PM Jun Liu  wrote:
> > > >
> > > > Hi, Community,
> > > >
> > > > On behalf of the Dubbo PPMC, I am pleased to announce that Minxuan
> > > Zhuang, whose github id is nzomkxia, has been voted in as a new Dubbo
> > > committer.
> > > >
> > > > He has did and is doing a great job on dubbo-ops, and I just want to
> > say
> > > thanks and congratulations. Please join me to say congratulations to
> > > Minxuan!
> > > >
> > > > Minxuan, would you please briefly introduce yourself to the
> community?
> > > >
> > > > Best regards,
> > > > Jun
> > > >
> > >
> > >
> > > --
> > > Best Regards！
> > > Huxing
> > >
> >
>

Re: Local forced trigger mock does not take effect

[Zonghai Shang]

I have found it , I will fix it later.

yiji

jun liu  于2018年9月12日周三 下午12:45写道：

>
> >> 2. mock=“force:return xxx”, directly specify the return value you want.
> > This may be the case you want to use, but I think you just forget the
> mock
> > value you want.
> >
> > It does’t work, cause:
> > PropertyAccessException 1:
> > org.springframework.beans.MethodInvocationException: Property 'mock'
> threw
> > exception; nested exception is java.lang.IllegalStateException: Invalid
> > mock="force:return null" contain illegal charactor, only digit, letter,
> > '-', '_' and '.' is legal.
> >
> > I think maybe the implementation of mock may have bugs.
>
> I haven’t tried this usage in xml yet, seems like we need to find the
> problem and fix it so that it can work properly as expected.
>
> Best regards,
> Jun
>
> > On 12 Sep 2018, at 10:24, Zonghai Shang  wrote:
> >
> >> 1. mock=“true”, this will direct the to the default mock implementation
> > with a name convention like DemoServiceMock.
> >> 3. mock=“org.apache.dubbo.xxx.xxxMock”, specify the class where your
> mock
> > logic is located.
> >
> > mock=“org.apache.dubbo.xxx.xxxMock” , only throw RpcException to execute
> > the mock, which does not match the force logic.
> >
> >> 2. mock=“force:return xxx”, directly specify the return value you want.
> > This may be the case you want to use, but I think you just forget the
> mock
> > value you want.
> >
> > It does’t work, cause:
> > PropertyAccessException 1:
> > org.springframework.beans.MethodInvocationException: Property 'mock'
> threw
> > exception; nested exception is java.lang.IllegalStateException: Invalid
> > mock="force:return null" contain illegal charactor, only digit, letter,
> > '-', '_' and '.' is legal.
> >
> > I think maybe the implementation of mock may have bugs.
> >
> >
> > Best regards,
> > yiji
> >
> > jun liu  于2018年9月12日周三 上午8:56写道：
> >
> >>>  >>> interface="com.alibaba.dubbo.samples.mock.api.DemoService"
> mock="force”/>
> >>
> >> As far as I can describe now, I think you can use:
> >> 1. mock=“true”, this will direct the to the default mock implementation
> >> with a name convention like DemoServiceMock.
> >> 2. mock=“force:return xxx”, directly specify the return value you want.
> >> This may be the case you want to use, but I think you just forget the
> mock
> >> value you want.
> >> 3. mock=“org.apache.dubbo.xxx.xxxMock”, specify the class where your
> mock
> >> logic is located.
> >>
> >>> `com.alibaba.dubbo.common.utils.ConfigUtils#isDefault` should support
> >>> force? Can someone help me?
> >>
> >> Given the above usage supported I think there’s no need to add an extra
> >> mock=“force” support. What do u think?
> >>
> >> Best regards,
> >> Jun
> >>
> >>> On 11 Sep 2018, at 16:31, Zonghai Shang  wrote:
> >>>
> >>> Hi,
> >>>
> >>> MockClusterInvoker provides local forced mock，I tested it locally, but
> it
> >>> doesn't work.
> >>>
> >>> @Override
> >>> public Result invoke(Invocation invocation) throws RpcException {
> >>>   // ….
> >>>   else if (value.startsWith("force")) {
> >>>   if (logger.isWarnEnabled()) {
> >>>   logger.info("force-mock: " + invocation.getMethodName() + "
> >>> force-mock enabled , url : " + directory.getUrl());
> >>>   }
> >>>   //force:direct mock
> >>>   result = doMockInvoke(invocation, null);
> >>>   }
> >>>  // ….
> >>> }
> >>>
> >>>  >>> interface="com.alibaba.dubbo.samples.mock.api.DemoService"
> mock="force”/>
> >>>
> >>> Here is demo:
> >>> https://github.com/dubbo/dubbo-samples/tree/master/dubbo-samples-mock
> >>>
> >>> `com.alibaba.dubbo.common.utils.ConfigUtils#isDefault` should support
> >>> force? Can someone help me?
> >>>
> >>> yiji
> >>
> >>
>
>

回复：关于dubbo的版本

[秦金卫]

2.8.× is the dubbox version，not dubbo，dubbo Only 2.6.x and 2.7.x




| |
秦金卫
邮箱：kimmk...@163.com
|

签名由 网易邮箱大师 定制

在2018年09月12日 11:00，宗荣 写道：
http://mvnrepository.com/artifact/com.alibaba/dubbo这个是dubbo版本的官方地址吗，里面的最新版本是2.6.3，但我看网上有一些版本已经到了2.8.4，我是一名刚开始学习dubbo的开发人员，不知能否帮忙解答下，谢谢！

Re: [ANNOUNCE] Welcome new committer Minxuan Zhuang

[Ian Luo]

Congratulations!

On Wed, Sep 12, 2018 at 1:29 PM Jerrick Zhu  wrote:

> Congrats.
>
> On Wed, Sep 12, 2018 at 11:44 AM Zonghai Shang  wrote:
>
> > Congratulations!
> >
> > yiji
> >
> > yuhang xiu  于2018年9月12日周三 上午10:09写道：
> >
> > > Congratulations!
> > > Welcome to Dubbo. :)
> > >
> > > Huxing Zhang  于2018年9月12日周三 上午7:26写道：
> > >
> > > > Congratulations!
> > > > On Tue, Sep 11, 2018 at 8:39 PM Jun Liu  wrote:
> > > > >
> > > > > Hi, Community,
> > > > >
> > > > > On behalf of the Dubbo PPMC, I am pleased to announce that Minxuan
> > > > Zhuang, whose github id is nzomkxia, has been voted in as a new Dubbo
> > > > committer.
> > > > >
> > > > > He has did and is doing a great job on dubbo-ops, and I just want
> to
> > > say
> > > > thanks and congratulations. Please join me to say congratulations to
> > > > Minxuan!
> > > > >
> > > > > Minxuan, would you please briefly introduce yourself to the
> > community?
> > > > >
> > > > > Best regards,
> > > > > Jun
> > > > >
> > > >
> > > >
> > > > --
> > > > Best Regards！
> > > > Huxing
> > > >
> > >
> >
>

Re: [DISCUSS] A metric to measure the response time to issues/prs

[Jerrick Zhu]

On Wed, Sep 12, 2018 at 12:53 PM Huxing Zhang  wrote:

> Hi,
>
> I just find an article [1] complaining about the response time to pull
> request and issues.
>

That's true. Our issue/PR's response time is too long.


>
> I think we can use a metric to measure the response time, and I found this
> [2].
>
> It looks like we are not doing very well.
>
> Does the community think it is useful to have such an metric?
>

A metric is just a way but not a solution.

Actually we need to call for the whole community to join, respond to
issues, review PRs. But this must start from the PPMC and committers.


>
> Is there anything we can do to improve it?
>
> [1] https://paper.tuisec.win/detail/0990f6a290f042e
> [2] https://isitmaintained.com/project/apache/incubator-dubbo
>
> --
> Best Regards！
> Huxing
>

Re: current status of dubbo ops

[jun liu]

> if you are interested in this project, please consider to accomplish
> service governance pages(dynamic config, load balance, etc.), the layout is
> similar with the current routing rule page, and submit pr to develop
> branch, thanks

Some guys in community and I are working with the new format of configuration 
rules in Dubbo Framework including dynamic configuration and routing rules 
which is expected to be released as part of v2.7.0. I think we need to discuss 
the format of these configuration rules together since OPS works as the entry 
point of all the configuration operations and the Dubbo framework will 
recognise the configuration format released by OPS. 

The codes are located mainly in this branch[1] and some PRs[2]. I am writing 
down the design purposes of some important changes and a rough idea of the 
format of the configuration format I have got in mind, I will publish it to 
here or github for further discussion once finished.

1. https://github.com/apache/incubator-dubbo/tree/dev-metadata
2. https://github.com/apache/incubator-dubbo/pull/2468

Best regards,
Jun

> On 10 Sep 2018, at 23:36, Minxuan Zhuang  wrote:
> 
> dubbo ops is under refactoring, here is some progress status:
> 1 the current working branch is *develop*,
> 2 the monitor and registry module have been removed
> 3 prototype of 'service search' and 'routing rule' are accomplished
> 4. new readme about how to build the front end and back end
> 
> if you are interested in this project, please consider to accomplish
> service governance pages(dynamic config, load balance, etc.), the layout is
> similar with the current routing rule page, and submit pr to develop
> branch, thanks

Re: The effect of Provider async on the Consumer side

[yuhang xiu]

Hi, community,
After checking the code and discussion, I think it would be better if you
fix this problem at both ends.

1. On the Provider side, the method.async is not exposed to ensure
compatibility.
2. Ignore the Provider's method.async property on the Consumer side to
ensure that the Provider's method.async does not affect the Consumer's
behavior.

In the future, when OPS shows the asynchronous situation of the provider,
we just need to let the provider still register the method.async property.

ISSUE is here, there are some discussion, too:
https://github.com/apache/incubator-dubbo/issues/2321

Huxing Zhang  于2018年9月12日周三 上午9:46写道：

> On Mon, Sep 10, 2018 at 10:10 AM yuhang xiu  wrote:
> >
> > Hi Huxing,
> > This is because there is a bug that causes them to be inconsistent. We
> > removed the async attribute from the Provider in ClusterUtil, but did not
> > remove the method.async attribute, causing the Provider's method.async to
> > affect the Consumer side.
> >
> > We don't need extra configuration, we just need to remove method.async in
> > ClusterUtil to solve this problem, and we don't need to modify the URL of
> > the Provider registered in the registry.
>
>
> Thanks for the explanation, it looks good to me!
>
> >
> > Huxing Zhang  于2018年9月7日周五 下午11:40写道：
> >
> > > Hi,
> > >
> > > On Wed, Sep 5, 2018 at 3:30 PM yuhang xiu  wrote:
> > > >
> > > > Hi community,
> > > >
> > > > Recently I found a bug[1] in the issue list (submitted by the
> > > > https://github.com/fingthinking user), which has been verified to be
> > > valid.
> > > > The root cause of the problem is that the Provider registered the
> > > > method.async to the registry and finally affected the Consumer side.
> > > >
> > > > The user submitted pr[2] to fix the problem. The fix is that the
> provider
> > > > does not register the method.async to the registry, so the Consumer
> side
> > > > cannot perceive it.
> > > > I think this way is not the best. I think the best way is that the
> > > Provider
> > > > side still registers method.async to the registry, but the Consumer
> side
> > > > ignores this property.
> > >
> > > Do you have any idea how to achieve this? Do we need to have extra
> > > configuration on consumer side?
> > > Or is it a special case?
> > >
> > > > The advantage is that in the future we can still see
> > > > the asynchronous situation of the various methods of the provider on
> > > > dubbo-ops,
> > >
> > > +1
> > >
> > > > and this processing method is more in line with the purpose of
> > > > dubbo configuration coverage.
> > > >
> > > > What do you think about it?
> > > >
> > > > [1]https://github.com/apache/incubator-dubbo/issues/2321
> > > > [2]https://github.com/apache/incubator-dubbo/pull/2322
> > >
> > > I also noticed that you have replied on the issue:
> > >
> > > > When using , the Consumer will not
> be
> > > affected. However, the Consumer call will be affected when using
> > > .
> > >
> > > Why they are not consistent?
> > >
> > > --
> > > Best Regards！
> > > Huxing
> > >
>
>
>
> --
> Best Regards！
> Huxing
>

about grpc support

[????????]

hello:


  dubbo grpcfeaturegrpc 
streaminggrpc stub layerexport?? refer?? 
invokergrpc


??




Best Regards,
dp

Re: Local forced trigger mock does not take effect

[Ian Luo]

ZhongHai,

Would you mind to fire an issue on GitHub?

Thanks,
-Ian.


On Tue, Sep 11, 2018 at 4:32 PM Zonghai Shang  wrote:

> Sorry, invoke refer
> here:
> com.alibaba.dubbo.rpc.cluster.support.wrapper.MockClusterInvoker#invoke
>
> Zonghai Shang  于2018年9月11日周二 下午4:31写道：
>
> > Hi,
> >
> > MockClusterInvoker provides local forced mock，I tested it locally, but it
> > doesn't work.
> >
> > @Override
> > public Result invoke(Invocation invocation) throws RpcException {
> > // ….
> > else if (value.startsWith("force")) {
> > if (logger.isWarnEnabled()) {
> > logger.info("force-mock: " + invocation.getMethodName() + "
> > force-mock enabled , url : " + directory.getUrl());
> > }
> > //force:direct mock
> > result = doMockInvoke(invocation, null);
> > }
> >// ….
> > }
> >
> >  > interface="com.alibaba.dubbo.samples.mock.api.DemoService" mock="force”/>
> >
> > Here is demo:
> > https://github.com/dubbo/dubbo-samples/tree/master/dubbo-samples-mock
> >
> > `com.alibaba.dubbo.common.utils.ConfigUtils#isDefault` should support
> > force? Can someone help me?
> >
> > yiji
> >
>

Re: Local forced trigger mock does not take effect

[Zonghai Shang]

Hi lan luo,

Yeah, I have recorded and tracked， refer :
https://github.com/apache/incubator-dubbo/issues/2489

Thanks for your reply,
yiji

Ian Luo  于2018年9月11日周二 下午11:00写道：

> ZhongHai,
>
> Would you mind to fire an issue on GitHub?
>
> Thanks,
> -Ian.
>
>
> On Tue, Sep 11, 2018 at 4:32 PM Zonghai Shang  wrote:
>
> > Sorry, invoke refer
> > here:
> > com.alibaba.dubbo.rpc.cluster.support.wrapper.MockClusterInvoker#invoke
> >
> > Zonghai Shang  于2018年9月11日周二 下午4:31写道：
> >
> > > Hi,
> > >
> > > MockClusterInvoker provides local forced mock，I tested it locally, but
> it
> > > doesn't work.
> > >
> > > @Override
> > > public Result invoke(Invocation invocation) throws RpcException {
> > > // ….
> > > else if (value.startsWith("force")) {
> > > if (logger.isWarnEnabled()) {
> > > logger.info("force-mock: " + invocation.getMethodName() +
> "
> > > force-mock enabled , url : " + directory.getUrl());
> > > }
> > > //force:direct mock
> > > result = doMockInvoke(invocation, null);
> > > }
> > >// ….
> > > }
> > >
> > >  > > interface="com.alibaba.dubbo.samples.mock.api.DemoService"
> mock="force”/>
> > >
> > > Here is demo:
> > > https://github.com/dubbo/dubbo-samples/tree/master/dubbo-samples-mock
> > >
> > > `com.alibaba.dubbo.common.utils.ConfigUtils#isDefault` should support
> > > force? Can someone help me?
> > >
> > > yiji
> > >
> >
>

Re: I add a Scala sample, do you have an interest in it?

[Kun Song]

Thanks, I will add more if I get one :)

> 在 2018年9月11日，下午10:33，Ian Luo  写道：
> 
> Yes, it's been fixed. Any other sample planed to add, BTW :)
> 
> Thanks,
> -Ian.
> 
> On Tue, Sep 11, 2018 at 4:15 PM Kun Song  wrote:
> 
>> Sorry for my delay.
>> 
>> Does the new maven fix it? If not, l will fix the code this night :)
>> 
>> 发自我的 iPhone
>> 
>>> 在 2018年9月11日，下午3:46，Ian Luo  写道：
>>> 
>>> Kun, I merged your code.
>>> 
>>> -Ian.
>>> 
 On Tue, Sep 11, 2018 at 2:11 PM Ian Luo  wrote:
 
 Kun, your scala sample looks pretty good. I kicked a new build just now,
 let's see how it's going for this time.
 
> On Tue, Sep 11, 2018 at 2:03 PM Ian Luo  wrote:
> 
> Kun,
> 
> It fails with
> 
> [ERROR] Failed to execute goal
>> net.alchim31.maven:scala-maven-plugin:3.3.3:compile (default) on
>> project
>> dubbo-samples-scala: The plugin
>> net.alchim31.maven:scala-maven-plugin:3.3.3
>> requires Maven version 3.5.3 -> [Help 1]
> 
> 
> I upgrade maven to 3.5.4, pls. merge the latest change and try it
>> again.
> 
> -Ian.
> 
> 
>> On Tue, Sep 11, 2018 at 10:15 AM YunKun Huang 
>> wrote:
>> 
>> It's good to have a scala sample, but I notice the CI fail in your PR.
>> 
>> ```
>> Failed to execute goal
>> net.alchim31.maven:scala-maven-plugin:3.3.3:compile (default) on
>> project
>> dubbo-samples-scala: The plugin
>> net.alchim31.maven:scala-maven-plugin:3.3.3
>> requires Maven version 3.5.3
>> ```
>> 
>>> On 2018/09/11 00:22:34, Kun Song  wrote:
>>> Hi community, I add a Dubbo sample with Scala(not merge yet), aiming
>> to equip our user with the power of Scala
>>> 
>>> And if you’re interested in it, you can review the PR here
>> https://github.com/dubbo/dubbo-samples/pull/28 <
>> https://github.com/dubbo/dubbo-samples/pull/28>.
>>> 
>>> Happy for any feedback :)
>> 
> 
>> 

Re: [openzipkin/brave] Add Api configuration demo for dubbo (#632)

[Adrian Cole]

following-up here https://github.com/alibaba/dubbo-spring-boot-starter/issues/53

Podling Report Reminder - March 2018

[johndament]

Dear podling,

This email was sent by an automated system on behalf of the Apache
Incubator PMC. It is an initial reminder to give you plenty of time to
prepare your quarterly board report.

The board meeting is scheduled for Wed, 21 March 2018, 10:30 am PDT.
The report for your podling will form a part of the Incubator PMC
report. The Incubator PMC requires your report to be submitted 2 weeks
before the board meeting, to allow sufficient time for review and
submission (Wed, March 07).

Please submit your report with sufficient time to allow the Incubator
PMC, and subsequently board members to review and digest. Again, the
very latest you should submit your report is 2 weeks prior to the board
meeting.

Thanks,

The Apache Incubator PMC

Submitting your Report

--

Your report should contain the following:

*   Your project name
*   A brief description of your project, which assumes no knowledge of
the project or necessarily of its field
*   A list of the three most important issues to address in the move
towards graduation.
*   Any issues that the Incubator PMC or ASF Board might wish/need to be
aware of
*   How has the community developed since the last report
*   How has the project developed since the last report.
*   How does the podling rate their own maturity.

This should be appended to the Incubator Wiki page at:

https://wiki.apache.org/incubator/March2018

Note: This is manually populated. You may need to wait a little before
this page is created from a template.

Mentors
---

Mentors should review reports for their project(s) and sign them off on
the Incubator wiki page. Signing off reports shows that you are
following the project - projects that are not signed may raise alarms
for the Incubator PMC.

Incubator PMC

Consumer side Validation SPI is wrongly activated while setting validation=true for provider

[Sunshow]

ATT.

this case consumer leads to throw

Caused by: java.lang.NoClassDefFoundError: javax/validation/Validation

even while calling no validation method, unless add all validation
dependencies to consumer,

that's not awesome, consumer side check should be activated by consumer
self.

one more question about ValidationFilter:

why the condition check is isNotEmpty:
ConfigUtils.isNotEmpty(invoker.getUrl().getMethodParameter(invocation.getMethodName(),
Constants.VALIDATION_KEY))

and previous version check true or false:
if (invoker.getUrl().getMethodParameter(invocation.getMethodName(),
Constants.VALIDATION_KEY, false))


Below is the reply from @ken.lj:


I think it is reasonable to check validation conditions on consumer side
before params passed to provider side as this can be more efficient. If we
keep it this way, we will meet the problem in your case: all consumers have
to be aware of provider side validation configurations, for example when
provider opened validation check, consumer side have to add necessary
dependencies.

Please, send this problem to dev@dubbo.apache.org, and subscribe to this
email address . We can decide
which way to go after a full discussion.

Re: Consumer side Validation SPI is wrongly activated while setting validation=true for provider

[Ian Luo]

Hi Sunshow,

Could you pls. attach a test case to reproduce the issue you described
here? I'd like to further investigate once I receive the reproducer.

Thanks,
-Ian.


On Wed, Mar 7, 2018 at 2:14 PM, Sunshow  wrote:

> ATT.
>
> this case consumer leads to throw
>
> Caused by: java.lang.NoClassDefFoundError: javax/validation/Validation
>
> even while calling no validation method, unless add all validation
> dependencies to consumer,
>
> that's not awesome, consumer side check should be activated by consumer
> self.
>
> one more question about ValidationFilter:
>
> why the condition check is isNotEmpty:
> ConfigUtils.isNotEmpty(invoker.getUrl().getMethodParameter(invocation.
> getMethodName(),
> Constants.VALIDATION_KEY))
>
> and previous version check true or false:
> if (invoker.getUrl().getMethodParameter(invocation.getMethodName(),
> Constants.VALIDATION_KEY, false))
>
>
> Below is the reply from @ken.lj:
>
>
> I think it is reasonable to check validation conditions on consumer side
> before params passed to provider side as this can be more efficient. If we
> keep it this way, we will meet the problem in your case: all consumers have
> to be aware of provider side validation configurations, for example when
> provider opened validation check, consumer side have to add necessary
> dependencies.
>
> Please, send this problem to dev@dubbo.apache.org, and subscribe to this
> email address . We can
> decide
> which way to go after a full discussion.
>

Re: On a user list

[Mark Thomas]

On 08/03/18 08:09, jun liu wrote:
> Thanks for your advice to dubbo community, Adrian. 
> 
> I agree with the potential problems or even challenges you mentioned. But 
> when other channels are not forced to be closed, people can still have 
> discussions on github issues or gitter channels, only remember to bring the 
> decision making ones here the @dev list.

My strong recommendation is that all development discussion moves to the
dev@ list.

Projects can have a range of user support channels (IRC, Gitter,
HipChat, mailing list, Stack overflow) as the project feels necessary.

> Finally, i’d like to see the github issue to be a pure place for tracking 
> determined requirements, enhancements, bugs or high suspicious bugs,

That seems sensible to me. Mixing bugs and support issues in the same
tracker might make it hard for people to work with.

> while casual discussions or decisions can be raised here. I don’t know  
> whether a github issue should working that way, but a user/dev list would 
> definitely helps to reach there, so i would choose to be a good boy and 
> follow the mentor’s guidance, see what will happen using both mailing list 
> and github issue at the incubator phase.
> 
> I expect to see the amazing features happen: any issues raised with apache 
> github will be sent to the @dev list automatically after a proper repo 
> migration.

Given Dubbo has an issues@ list I'd expect it to go there but the Dubbo
community can choose how it wants to handle that.

Mark


> Also only my own opinion, a new fellow in apache and the github community.
> 
> Best regards,
> Jun Liu
> 
> 
>> On 7 Mar 2018, at 4:46 PM, Adrian Cole  wrote:
>>
>> Hi, folks.
>>
>> I understand that conventionally apache incubator projects don't have
>> user lists. I suspect someone more familiar can give the whole story
>> on that, but I assume the rationale is to be a bit cautious while the
>> project matures. Notably, this is maturing in the Apache way, conduct
>> and community.
>>
>> That said, I was a bit alarmed to see a suggestion that all users
>> should be routed to the dev list from github.
>> https://github.com/alibaba/dubbo/issues/1393
>>
>> The reason I was concerned was just the huge following dubbo has..
>> 2.7k watchers if not ignoring will receive this advice :) Perhaps
>> prematurely, I'm worried that redirecting routine users to the dev
>> list will be hard to undo once people establish a pattern. I feel we
>> could stop that pattern up-front by having a user list and suggesting
>> that instead.
>>
>> Please bear in mind that I don't have a lot of experience with dubbo
>> and people communicating on the "wrong list" isn't necessarily bad. I
>> might just be a bit scared due to the scale of the existing community
>> here.
>>
>> Thoughts welcome, and if none, thanks for letting me express myself :)
>>
>> -A
> 

Re: On a user list

[jun liu]

Thanks for your advice to dubbo community, Adrian. 

I agree with the potential problems or even challenges you mentioned. But when 
other channels are not forced to be closed, people can still have discussions 
on github issues or gitter channels, only remember to bring the decision making 
ones here the @dev list. Finally, i’d like to see the github issue to be a pure 
place for tracking determined requirements, enhancements, bugs or high 
suspicious bugs, while casual discussions or decisions can be raised here. I 
don’t know  whether a github issue should working that way, but a user/dev list 
would definitely helps to reach there, so i would choose to be a good boy and 
follow the mentor’s guidance, see what will happen using both mailing list and 
github issue at the incubator phase.

I expect to see the amazing features happen: any issues raised with apache 
github will be sent to the @dev list automatically after a proper repo 
migration.

Also only my own opinion, a new fellow in apache and the github community.

Best regards,
Jun Liu


> On 7 Mar 2018, at 4:46 PM, Adrian Cole  wrote:
> 
> Hi, folks.
> 
> I understand that conventionally apache incubator projects don't have
> user lists. I suspect someone more familiar can give the whole story
> on that, but I assume the rationale is to be a bit cautious while the
> project matures. Notably, this is maturing in the Apache way, conduct
> and community.
> 
> That said, I was a bit alarmed to see a suggestion that all users
> should be routed to the dev list from github.
> https://github.com/alibaba/dubbo/issues/1393
> 
> The reason I was concerned was just the huge following dubbo has..
> 2.7k watchers if not ignoring will receive this advice :) Perhaps
> prematurely, I'm worried that redirecting routine users to the dev
> list will be hard to undo once people establish a pattern. I feel we
> could stop that pattern up-front by having a user list and suggesting
> that instead.
> 
> Please bear in mind that I don't have a lot of experience with dubbo
> and people communicating on the "wrong list" isn't necessarily bad. I
> might just be a bit scared due to the scale of the existing community
> here.
> 
> Thoughts welcome, and if none, thanks for letting me express myself :)
> 
> -A

Ask for release process

[Jun Liu]

Hi, mentors

The dubbo core project has fixed some critical bugs and enhancements, and it 
should be released now according to the original plan, with version upgrade to 
2.5.10. But dubbo is in Apache Incubator now, should we start a vote before 
release?

There’s no doubt that from the next version, all processes from requirements 
collection, development to release should be fully discussed and voted by the 
community here before it is actually done. But this version may be a special 
one, most of the works have started before incubator, and also, some users 
really expect for patches in this version. The contents to be released, mainly 
bugfix and enhancements:

https://github.com/alibaba/dubbo/milestone/14 


Should we still raise a vote for the next release(2.5.10)?

Best regards,
Jun Liu

Re: On double dubbo starters

[Mark Thomas]

On 07/03/18 11:41, Ian Luo wrote:
> Hi Mark,
> 
> Pls. check my comments below.

Thanks for the additional information.

Until the code transitions to the ASF (which I hope is fairly soon), and
especially if the community needs a release, then you are able to
publish releases as you have done previously.

Once the code transitions to the ASF, the ASF release policy applies.
Depending on where you start from, it can take a little work to get
everything aligned to the policy but that only needs to be done once.

Mark


> 
> Thanks,
> -Ian.
> 
> 
>> On 7 Mar 2018, at 6:09 PM, Mark Thomas  wrote:
>>
>> On 07/03/18 09:49, Ian Luo wrote:
>>> Hi Adrian,
>>>
>>> First of all, my apology for the confusion. The project under dubbo [1] 
>>> group is the official project we plan to maintain in long term for Spring 
>>> Boot support. I encourage you try it first and share your feedback if 
>>> there’s any. 
>>>
>>> In order to not block Adrian’s work, I suggest to publish it with the 
>>> existing groupId/artifactId since we can always republish with the new 
>>> groupId/artifactId in the next release cycle after the transition finishes.
>>>
>>> To dubbo’s mentors, I am not sure if it is appropriated for my proposal. 
>>> Pls. correct me once you read the message since we plan to release 
>>> spring-boot-starter officially very soon (by the end of this week or the 
>>> early of the next week).
>>>
>>> Thanks,
>>> -Ian. 
>>>
>>> 1.  https://github.com/dubbo/dubbo-spring-boot-project 
>>
>> Hi,
>>
>> I need a little more information before offering an opinion.
>>
>> 1. Who is the "we" that intends to publish the release?
> 
> [iluo]: Here “we” means dubbo development team. 
> 
>>
>> 2. How will the release be named (including Maven co-ordinates)?
> 
> [iluo]: It will be com.alibaba.boot:dubbo-spring-boot-starter at this moment. 
> 
>>
>> 3. Is it intended that this code will become part of Apache Dubbo? If
>> so, what stage is this code at in its transition to the ASF?
> 
> [iluo]: It’s a side project [1] of Apache Dubbo. All projects under dubbo 
> group [2] will be included in this transition, you could check details from 
> JIRA issue DUBBO-3 [3].
> 
> 
> 1. https://github.com/dubbo/dubbo-spring-boot-project
> 2. https://github.com/dubbo
> 3. https://issues.apache.org/jira/projects/DUBBO/issues/DUBBO-3
> 
>>
>> Thanks,
>>
>> Mark
>>
>>
>>>
>>>
 On 7 Mar 2018, at 5:04 PM, Adrian Cole  wrote:

 Hi, all

 I'm working on spring-cloud-sleuth tracing integration with dubbo.
 We've had users requesting dubbo for a while now for spring boot
 applications.

 https://github.com/spring-cloud/spring-cloud-sleuth/issues/710

 One of the commitments we made was to have dubbo tracing included for
 spring boot 2 applications, leveraging the efforts we made in the
 Zipkin library Brave (which similarly had a backlog of dubbo
 interest).

 The good news is that, I've been able to get this working, which is 
 awesome.

 https://github.com/openzipkin/sleuth-webmvc-example/compare/add-dubbo-tracing

 I'm only waiting a couple small patches and we are ready to go! The
 community have been great and the plugin changes quickly in the right
 direction.

 I ran into a glitch as I was told that the plugin I use, the "alibaba"
 variant, is not official. Rather, the "dubbo" one was.

 https://github.com/alibaba/dubbo-spring-boot-starter < I am using this
 and it works
 https://github.com/dubbo/dubbo-spring-boot-project < haven't tried this, 
 yet

 I would like to try the other version, but it seems to be in release
 limbo. For example, it is not published anywhere and there are some
 concerns about publishing it while apache takes its course.

 https://issues.apache.org/jira/projects/DUBBO/issues/DUBBO-3

 Meanwhile, I actually like the plugin I am using and the person
 maintaining it is good. This is a tough situation to be in where what
 is working is not recommended, and what is recommended I have to build
 or consume snapshot of.

 How should we proceed on this?
 -A
> 
> 

Re: On a user list

[Ian Luo]

> On 8 Mar 2018, at 5:47 PM, Mark Thomas  wrote:
> 
> On 08/03/18 08:09, jun liu wrote:
>> Thanks for your advice to dubbo community, Adrian. 
>> 
>> I agree with the potential problems or even challenges you mentioned. But 
>> when other channels are not forced to be closed, people can still have 
>> discussions on github issues or gitter channels, only remember to bring the 
>> decision making ones here the @dev list.
> 
> My strong recommendation is that all development discussion moves to the
> dev@ list.
> 
> Projects can have a range of user support channels (IRC, Gitter,
> HipChat, mailing list, Stack overflow) as the project feels necessary.
> 
>> Finally, i’d like to see the github issue to be a pure place for tracking 
>> determined requirements, enhancements, bugs or high suspicious bugs,
> 
> That seems sensible to me. Mixing bugs and support issues in the same
> tracker might make it hard for people to work with.

This makes sense to me too. Github issue is a good place for general 
discussion, but we did experience too many irrelevant issues filed on dubbo 
issue. We plan to guide people to use dev mail list for general discussion so 
that we can spend less time in triaging github issues :)

> 
>> while casual discussions or decisions can be raised here. I don’t know  
>> whether a github issue should working that way, but a user/dev list would 
>> definitely helps to reach there, so i would choose to be a good boy and 
>> follow the mentor’s guidance, see what will happen using both mailing list 
>> and github issue at the incubator phase.
>> 
>> I expect to see the amazing features happen: any issues raised with apache 
>> github will be sent to the @dev list automatically after a proper repo 
>> migration.
> 
> Given Dubbo has an issues@ list I'd expect it to go there but the Dubbo
> community can choose how it wants to handle that.
> 
> Mark
> 
> 
>> Also only my own opinion, a new fellow in apache and the github community.
>> 
>> Best regards,
>> Jun Liu
>> 
>> 
>>> On 7 Mar 2018, at 4:46 PM, Adrian Cole  wrote:
>>> 
>>> Hi, folks.
>>> 
>>> I understand that conventionally apache incubator projects don't have
>>> user lists. I suspect someone more familiar can give the whole story
>>> on that, but I assume the rationale is to be a bit cautious while the
>>> project matures. Notably, this is maturing in the Apache way, conduct
>>> and community.
>>> 
>>> That said, I was a bit alarmed to see a suggestion that all users
>>> should be routed to the dev list from github.
>>> https://github.com/alibaba/dubbo/issues/1393
>>> 
>>> The reason I was concerned was just the huge following dubbo has..
>>> 2.7k watchers if not ignoring will receive this advice :) Perhaps
>>> prematurely, I'm worried that redirecting routine users to the dev
>>> list will be hard to undo once people establish a pattern. I feel we
>>> could stop that pattern up-front by having a user list and suggesting
>>> that instead.
>>> 
>>> Please bear in mind that I don't have a lot of experience with dubbo
>>> and people communicating on the "wrong list" isn't necessarily bad. I
>>> might just be a bit scared due to the scale of the existing community
>>> here.
>>> 
>>> Thoughts welcome, and if none, thanks for letting me express myself :)
>>> 
>>> -A
>> 
> 

Re: On double dubbo starters

[Ian Luo]

Sure, then we will not publish anything to maven repository until transition is 
done.

Adrian, I guess this decision shouldn’t stop your further development work 
since you could depend on the snapshot build anyway. We will try our best to 
work with Mark and other apache mentors to boost the transition as fast as 
possible.

Thanks,
-Ian.



> On 8 Mar 2018, at 5:40 PM, Mark Thomas  wrote:
> 
> On 07/03/18 11:41, Ian Luo wrote:
>> Hi Mark,
>> 
>> Pls. check my comments below.
> 
> Thanks for the additional information.
> 
> Until the code transitions to the ASF (which I hope is fairly soon), and
> especially if the community needs a release, then you are able to
> publish releases as you have done previously.
> 
> Once the code transitions to the ASF, the ASF release policy applies.
> Depending on where you start from, it can take a little work to get
> everything aligned to the policy but that only needs to be done once.
> 
> Mark
> 
> 
>> 
>> Thanks,
>> -Ian.
>> 
>> 
>>> On 7 Mar 2018, at 6:09 PM, Mark Thomas  wrote:
>>> 
>>> On 07/03/18 09:49, Ian Luo wrote:
 Hi Adrian,
 
 First of all, my apology for the confusion. The project under dubbo [1] 
 group is the official project we plan to maintain in long term for Spring 
 Boot support. I encourage you try it first and share your feedback if 
 there’s any. 
 
 In order to not block Adrian’s work, I suggest to publish it with the 
 existing groupId/artifactId since we can always republish with the new 
 groupId/artifactId in the next release cycle after the transition finishes.
 
 To dubbo’s mentors, I am not sure if it is appropriated for my proposal. 
 Pls. correct me once you read the message since we plan to release 
 spring-boot-starter officially very soon (by the end of this week or the 
 early of the next week).
 
 Thanks,
 -Ian. 
 
 1.  https://github.com/dubbo/dubbo-spring-boot-project 
>>> 
>>> Hi,
>>> 
>>> I need a little more information before offering an opinion.
>>> 
>>> 1. Who is the "we" that intends to publish the release?
>> 
>> [iluo]: Here “we” means dubbo development team. 
>> 
>>> 
>>> 2. How will the release be named (including Maven co-ordinates)?
>> 
>> [iluo]: It will be com.alibaba.boot:dubbo-spring-boot-starter at this 
>> moment. 
>> 
>>> 
>>> 3. Is it intended that this code will become part of Apache Dubbo? If
>>> so, what stage is this code at in its transition to the ASF?
>> 
>> [iluo]: It’s a side project [1] of Apache Dubbo. All projects under dubbo 
>> group [2] will be included in this transition, you could check details from 
>> JIRA issue DUBBO-3 [3].
>> 
>> 
>> 1. https://github.com/dubbo/dubbo-spring-boot-project
>> 2. https://github.com/dubbo
>> 3. https://issues.apache.org/jira/projects/DUBBO/issues/DUBBO-3
>> 
>>> 
>>> Thanks,
>>> 
>>> Mark
>>> 
>>> 
 
 
> On 7 Mar 2018, at 5:04 PM, Adrian Cole  wrote:
> 
> Hi, all
> 
> I'm working on spring-cloud-sleuth tracing integration with dubbo.
> We've had users requesting dubbo for a while now for spring boot
> applications.
> 
> https://github.com/spring-cloud/spring-cloud-sleuth/issues/710
> 
> One of the commitments we made was to have dubbo tracing included for
> spring boot 2 applications, leveraging the efforts we made in the
> Zipkin library Brave (which similarly had a backlog of dubbo
> interest).
> 
> The good news is that, I've been able to get this working, which is 
> awesome.
> 
> https://github.com/openzipkin/sleuth-webmvc-example/compare/add-dubbo-tracing
> 
> I'm only waiting a couple small patches and we are ready to go! The
> community have been great and the plugin changes quickly in the right
> direction.
> 
> I ran into a glitch as I was told that the plugin I use, the "alibaba"
> variant, is not official. Rather, the "dubbo" one was.
> 
> https://github.com/alibaba/dubbo-spring-boot-starter < I am using this
> and it works
> https://github.com/dubbo/dubbo-spring-boot-project < haven't tried this, 
> yet
> 
> I would like to try the other version, but it seems to be in release
> limbo. For example, it is not published anywhere and there are some
> concerns about publishing it while apache takes its course.
> 
> https://issues.apache.org/jira/projects/DUBBO/issues/DUBBO-3
> 
> Meanwhile, I actually like the plugin I am using and the person
> maintaining it is good. This is a tough situation to be in where what
> is working is not recommended, and what is recommended I have to build
> or consume snapshot of.
> 
> How should we proceed on this?
> -A
>> 
>> 
> 

Re: On a user list

[Huxing Zhang]

Hi,

On Thu, Mar 8, 2018 at 5:47 PM, Mark Thomas  wrote:
> On 08/03/18 08:09, jun liu wrote:
>> Thanks for your advice to dubbo community, Adrian.
>>
>> I agree with the potential problems or even challenges you mentioned. But 
>> when other channels are not forced to be closed, people can still have 
>> discussions on github issues or gitter channels, only remember to bring the 
>> decision making ones here the @dev list.
>
> My strong recommendation is that all development discussion moves to the
> dev@ list.
>
> Projects can have a range of user support channels (IRC, Gitter,
> HipChat, mailing list, Stack overflow) as the project feels necessary.
>
>> Finally, i’d like to see the github issue to be a pure place for tracking 
>> determined requirements, enhancements, bugs or high suspicious bugs,
>
> That seems sensible to me. Mixing bugs and support issues in the same
> tracker might make it hard for people to work with.
>
>> while casual discussions or decisions can be raised here. I don’t know  
>> whether a github issue should working that way, but a user/dev list would 
>> definitely helps to reach there, so i would choose to be a good boy and 
>> follow the mentor’s guidance, see what will happen using both mailing list 
>> and github issue at the incubator phase.
>>
>> I expect to see the amazing features happen: any issues raised with apache 
>> github will be sent to the @dev list automatically after a proper repo 
>> migration.
>
> Given Dubbo has an issues@ list I'd expect it to go there but the Dubbo
> community can choose how it wants to handle that.

+1 for separating dev@ and issues@

>
> Mark
>
>
>> Also only my own opinion, a new fellow in apache and the github community.
>>
>> Best regards,
>> Jun Liu
>>
>>
>>> On 7 Mar 2018, at 4:46 PM, Adrian Cole  wrote:
>>>
>>> Hi, folks.
>>>
>>> I understand that conventionally apache incubator projects don't have
>>> user lists. I suspect someone more familiar can give the whole story
>>> on that, but I assume the rationale is to be a bit cautious while the
>>> project matures. Notably, this is maturing in the Apache way, conduct
>>> and community.
>>>
>>> That said, I was a bit alarmed to see a suggestion that all users
>>> should be routed to the dev list from github.
>>> https://github.com/alibaba/dubbo/issues/1393
>>>
>>> The reason I was concerned was just the huge following dubbo has..
>>> 2.7k watchers if not ignoring will receive this advice :) Perhaps
>>> prematurely, I'm worried that redirecting routine users to the dev
>>> list will be hard to undo once people establish a pattern. I feel we
>>> could stop that pattern up-front by having a user list and suggesting
>>> that instead.
>>>
>>> Please bear in mind that I don't have a lot of experience with dubbo
>>> and people communicating on the "wrong list" isn't necessarily bad. I
>>> might just be a bit scared due to the scale of the existing community
>>> here.
>>>
>>> Thoughts welcome, and if none, thanks for letting me express myself :)
>>>
>>> -A
>>
>

-- 
Best Regards！
Huxing

Re: Re: On double dubbo starters

[Kimm King]

I think mentor means in another thread:
 we could publish something to maven central repository as usual until 
transition is done.



KimmKing(kimmk...@163.com)
 == In me the tiger sniffs the rose. ==

 
From: Ian Luo
Date: 2018-03-08 21:40
To: dev
Subject: Re: On double dubbo starters
 
> On 8 Mar 2018, at 9:22 PM, Ian Luo  wrote:
> 
> Sure, then we will not publish anything to maven repository until transition 
> is done.
> 
 
Oops, I think I misunderstood. Mark, could you pls. confirm we could still 
publish release from the “old” repositories during the transition?
 
Thanks,
-Ian.
 
 
> Adrian, I guess this decision shouldn’t stop your further development work 
> since you could depend on the snapshot build anyway. We will try our best to 
> work with Mark and other apache mentors to boost the transition as fast as 
> possible.
> 
> Thanks,
> -Ian.
> 
> 
> 
>> On 8 Mar 2018, at 5:40 PM, Mark Thomas  wrote:
>> 
>> On 07/03/18 11:41, Ian Luo wrote:
>>> Hi Mark,
>>> 
>>> Pls. check my comments below.
>> 
>> Thanks for the additional information.
>> 
>> Until the code transitions to the ASF (which I hope is fairly soon), and
>> especially if the community needs a release, then you are able to
>> publish releases as you have done previously.
>> 
>> Once the code transitions to the ASF, the ASF release policy applies.
>> Depending on where you start from, it can take a little work to get
>> everything aligned to the policy but that only needs to be done once.
>> 
>> Mark
>> 
>> 
>>> 
>>> Thanks,
>>> -Ian.
>>> 
>>> 
 On 7 Mar 2018, at 6:09 PM, Mark Thomas  wrote:
 
 On 07/03/18 09:49, Ian Luo wrote:
> Hi Adrian,
> 
> First of all, my apology for the confusion. The project under dubbo [1] 
> group is the official project we plan to maintain in long term for Spring 
> Boot support. I encourage you try it first and share your feedback if 
> there’s any. 
> 
> In order to not block Adrian’s work, I suggest to publish it with the 
> existing groupId/artifactId since we can always republish with the new 
> groupId/artifactId in the next release cycle after the transition 
> finishes.
> 
> To dubbo’s mentors, I am not sure if it is appropriated for my proposal. 
> Pls. correct me once you read the message since we plan to release 
> spring-boot-starter officially very soon (by the end of this week or the 
> early of the next week).
> 
> Thanks,
> -Ian. 
> 
> 1.  https://github.com/dubbo/dubbo-spring-boot-project 
 
 Hi,
 
 I need a little more information before offering an opinion.
 
 1. Who is the "we" that intends to publish the release?
>>> 
>>> [iluo]: Here “we” means dubbo development team. 
>>> 
 
 2. How will the release be named (including Maven co-ordinates)?
>>> 
>>> [iluo]: It will be com.alibaba.boot:dubbo-spring-boot-starter at this 
>>> moment. 
>>> 
 
 3. Is it intended that this code will become part of Apache Dubbo? If
 so, what stage is this code at in its transition to the ASF?
>>> 
>>> [iluo]: It’s a side project [1] of Apache Dubbo. All projects under dubbo 
>>> group [2] will be included in this transition, you could check details from 
>>> JIRA issue DUBBO-3 [3].
>>> 
>>> 
>>> 1. https://github.com/dubbo/dubbo-spring-boot-project
>>> 2. https://github.com/dubbo
>>> 3. https://issues.apache.org/jira/projects/DUBBO/issues/DUBBO-3
>>> 
 
 Thanks,
 
 Mark
 
 
> 
> 
>> On 7 Mar 2018, at 5:04 PM, Adrian Cole  wrote:
>> 
>> Hi, all
>> 
>> I'm working on spring-cloud-sleuth tracing integration with dubbo.
>> We've had users requesting dubbo for a while now for spring boot
>> applications.
>> 
>> https://github.com/spring-cloud/spring-cloud-sleuth/issues/710
>> 
>> One of the commitments we made was to have dubbo tracing included for
>> spring boot 2 applications, leveraging the efforts we made in the
>> Zipkin library Brave (which similarly had a backlog of dubbo
>> interest).
>> 
>> The good news is that, I've been able to get this working, which is 
>> awesome.
>> 
>> https://github.com/openzipkin/sleuth-webmvc-example/compare/add-dubbo-tracing
>> 
>> I'm only waiting a couple small patches and we are ready to go! The
>> community have been great and the plugin changes quickly in the right
>> direction.
>> 
>> I ran into a glitch as I was told that the plugin I use, the "alibaba"
>> variant, is not official. Rather, the "dubbo" one was.
>> 
>> https://github.com/alibaba/dubbo-spring-boot-starter < I am using this
>> and it works
>> https://github.com/dubbo/dubbo-spring-boot-project < haven't tried this, 
>> yet
>> 
>> I would like to try the other version, but it seems to be in release
>> limbo. For example, it is 

Re: How to turn off the dubbo monitor log

[Ian Luo]

In order to turn off the log, you need to
specify com.alibaba.dubbo.monitor.dubbo.DubboMonitor log entry in your log
file and set its logging level above INFO.

On Fri, Mar 9, 2018 at 2:26 PM, ? ??  wrote:

> Dear all,
> How to turn off the dubbo monitor log
> e.g.
> [com.alibaba.dubbo.monitor.dubbo.DubboMonitor] [INFO] -  [DUBBO] Send
> statistics to monitor zookeeper://xxx:2181/com.alibaba.dubbo.monitor.
> MonitorService?anyhost=true=simple-monitor&
> check=false=-1=2.6.0=false=
> com.alibaba.dubbo.monitor.MonitorService=lookup,
> collect=qm=9669=1520089496318=2.6.0&
> side=provider=1520489737506, dubbo version: 2.6.0, current
> host: xxx
>
>
> Best Regards,
> Victor Zeng.
>

Re: Why heartbeatTimeout is 3 times as much as heartbeat?

[Ian Luo]

Hi Tian,

This is how the timeout default value is defined. You could always specify
timeout value by specify the URL parameter "Constants.HEARTBEAT_TIMEOUT_
KEY".

-Ian.

On Sat, Mar 10, 2018 at 5:58 PM, 天 <1197596...@qq.com> wrote:

> hi, I'm a little puzzled, why heartbeatTimeout is 3 times as much as
> heartbeat?
>
>
> public HeaderExchangeServer(Server server) {
> if (server == null) {
> throw new IllegalArgumentException("server == null");
> }
> this.server = server;
> this.heartbeat = server.getUrl().getParameter(Constants.HEARTBEAT_KEY,
> 0);
> this.heartbeatTimeout = server.getUrl().getParameter(
> Constants.HEARTBEAT_TIMEOUT_KEY, heartbeat * 3);
> if (heartbeatTimeout < heartbeat * 2) {
> throw new IllegalStateException("heartbeatTimeout <
> heartbeatInterval * 2");
> }
> startHeatbeatTimer();
> }

How to add Apache license head to the files of hessian-lite sub project

[Wang Xin]

Hi,all
   Now I’m adding Apache license head to the Dubbo project.  I find that 
,the hessian-lite sub project is totally  copied from hessian project 
(http://hessian.caucho.com/) , it’s package is modified and maintained here.
   The hessian project complies with Apache license 1.1. The license head in 
each file is as the following:
  What should I do with it?

/*
 * Copyright (c) 2001-2004 Caucho Technology, Inc.  All rights reserved.
 *
 * The Apache Software License, Version 1.1
 *
 * Redistribution and use in source and binary forms, with or without
 * modification, are permitted provided that the following conditions
 * are met:
 *
 * 1. Redistributions of source code must retain the above copyright
 *notice, this list of conditions and the following disclaimer.
 *
 * 2. Redistributions in binary form must reproduce the above copyright
 *notice, this list of conditions and the following disclaimer in
 *the documentation and/or other materials provided with the
 *distribution.
 *
 * 3. The end-user documentation included with the redistribution, if
 *any, must include the following acknowlegement:
 *   "This product includes software developed by the
 *Caucho Technology (http://www.caucho.com/)."
 *Alternately, this acknowlegement may appear in the software itself,
 *if and wherever such third-party acknowlegements normally appear.
 *
 * 4. The names "Burlap", "Resin", and "Caucho" must not be used to
 *endorse or promote products derived from this software without prior
 *written permission. For written permission, please contact
 *i...@caucho.com.
 *
 * 5. Products derived from this software may not be called "Resin"
 *nor may "Resin" appear in their names without prior written
 *permission of Caucho Technology.
 *
 * THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED
 * WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
 * OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
 * DISCLAIMED.  IN NO EVENT SHALL CAUCHO TECHNOLOGY OR ITS CONTRIBUTORS
 * BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY,
 * OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT
 * OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
 * BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
 * WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE
 * OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN
 * IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 *
 * @author Scott Ferguson
 */


Xin Wang
lovep...@hotmail.com

Re: On a user list

[Huxing Zhang]

+1 on moving to Github issue once a ticket is created.

On Fri, Mar 9, 2018 at 2:18 PM, Jun Liu  wrote:
>
> One more question. If we create an issue in github (or JIRA, not decided yet) 
> after having a discussion here the @dev list. How to ensure that the 
> discussions on both sides are synchronized after the creation of github 
> issue, because it seem reasonable to track on either side. For me it would 
> happen on github issue then.
>
>
>> On 8 Mar 2018, at 5:47 PM, Mark Thomas  wrote:
>>
>> On 08/03/18 08:09, jun liu wrote:
>>> Thanks for your advice to dubbo community, Adrian.
>>>
>>> I agree with the potential problems or even challenges you mentioned. But 
>>> when other channels are not forced to be closed, people can still have 
>>> discussions on github issues or gitter channels, only remember to bring the 
>>> decision making ones here the @dev list.
>>
>> My strong recommendation is that all development discussion moves to the
>> dev@ list.
>>
>> Projects can have a range of user support channels (IRC, Gitter,
>> HipChat, mailing list, Stack overflow) as the project feels necessary.
>>
>>> Finally, i’d like to see the github issue to be a pure place for tracking 
>>> determined requirements, enhancements, bugs or high suspicious bugs,
>>
>> That seems sensible to me. Mixing bugs and support issues in the same
>> tracker might make it hard for people to work with.
>>
>>> while casual discussions or decisions can be raised here. I don’t know  
>>> whether a github issue should working that way, but a user/dev list would 
>>> definitely helps to reach there, so i would choose to be a good boy and 
>>> follow the mentor’s guidance, see what will happen using both mailing list 
>>> and github issue at the incubator phase.
>>>
>>> I expect to see the amazing features happen: any issues raised with apache 
>>> github will be sent to the @dev list automatically after a proper repo 
>>> migration.
>>
>> Given Dubbo has an issues@ list I'd expect it to go there but the Dubbo
>> community can choose how it wants to handle that.
>>
>> Mark
>>
>>
>>> Also only my own opinion, a new fellow in apache and the github community.
>>>
>>> Best regards,
>>> Jun Liu
>>>
>>>
 On 7 Mar 2018, at 4:46 PM, Adrian Cole  wrote:

 Hi, folks.

 I understand that conventionally apache incubator projects don't have
 user lists. I suspect someone more familiar can give the whole story
 on that, but I assume the rationale is to be a bit cautious while the
 project matures. Notably, this is maturing in the Apache way, conduct
 and community.

 That said, I was a bit alarmed to see a suggestion that all users
 should be routed to the dev list from github.
 https://github.com/alibaba/dubbo/issues/1393

 The reason I was concerned was just the huge following dubbo has..
 2.7k watchers if not ignoring will receive this advice :) Perhaps
 prematurely, I'm worried that redirecting routine users to the dev
 list will be hard to undo once people establish a pattern. I feel we
 could stop that pattern up-front by having a user list and suggesting
 that instead.

 Please bear in mind that I don't have a lot of experience with dubbo
 and people communicating on the "wrong list" isn't necessarily bad. I
 might just be a bit scared due to the scale of the existing community
 here.

 Thoughts welcome, and if none, thanks for letting me express myself :)

 -A
>>>
>>
>

-- 
Best Regards！
Huxing

Re: How to add Apache license head to the files of hessian-lite sub project

[Kimm King]

I think keeping the notice is awesome.



KimmKing(kimmk...@163.com)
 == In me the tiger sniffs the rose. ==

 
发件人： Wang Xin
发送时间： 2018-03-12 18:01
收件人： dev@dubbo.apache.org
主题： How to add Apache license head to the files of hessian-lite sub project
Hi,all
   Now I’m adding Apache license head to the Dubbo project.  I find that 
,the hessian-lite sub project is totally  copied from hessian project 
(http://hessian.caucho.com/) , it’s package is modified and maintained here.
   The hessian project complies with Apache license 1.1. The license head in 
each file is as the following:
  What should I do with it?
 
/*
* Copyright (c) 2001-2004 Caucho Technology, Inc.  All rights reserved.
*
* The Apache Software License, Version 1.1
*
* Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that the following conditions
* are met:
*
* 1. Redistributions of source code must retain the above copyright
*notice, this list of conditions and the following disclaimer.
*
* 2. Redistributions in binary form must reproduce the above copyright
*notice, this list of conditions and the following disclaimer in
*the documentation and/or other materials provided with the
*distribution.
*
* 3. The end-user documentation included with the redistribution, if
*any, must include the following acknowlegement:
*   "This product includes software developed by the
*Caucho Technology (http://www.caucho.com/)."
*Alternately, this acknowlegement may appear in the software itself,
*if and wherever such third-party acknowlegements normally appear.
*
* 4. The names "Burlap", "Resin", and "Caucho" must not be used to
*endorse or promote products derived from this software without prior
*written permission. For written permission, please contact
*i...@caucho.com.
*
* 5. Products derived from this software may not be called "Resin"
*nor may "Resin" appear in their names without prior written
*permission of Caucho Technology.
*
* THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED
* WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
* OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
* DISCLAIMED.  IN NO EVENT SHALL CAUCHO TECHNOLOGY OR ITS CONTRIBUTORS
* BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY,
* OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT
* OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
* BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
* WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE
* OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN
* IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
*
* @author Scott Ferguson
*/
 
 
Xin Wang
lovep...@hotmail.com
 
 
 

The problem of deploying Dubbo to K8S

[????]

Dear all
Good day.
I have been confronted with a problem recently. I deploy the Dubbo container 
project on K8S. When I found out in this way 
(https://github.com/dubbo/dubbo-docker-sample), it was easy to cause the host 
port conflict. Is there a way to implement service registration and service 
discovery in a docker container directly?


This is the history issues from github.Please check 
it.(https://github.com/alibaba/dubbo/issues/1441)
Glad to contact with you.Thanks & Best Regards,
Little Ma

Re: Why heartbeatTimeout is 3 times as much as heartbeat?

[jun liu]

> hi, I'm a little puzzled, why heartbeatTimeout is 3 times as much as 
> heartbeat?


Heart determines the interval to detect, while heartbeatTimeout determines when 
to announce the connection is broken. 
3 times is the maximum heartbeat failures dubbo can bear before mark a 
connection as broken.

> On 10 Mar 2018, at 5:58 PM, 天 <1197596...@qq.com> wrote:
> 
> hi, I'm a little puzzled, why heartbeatTimeout is 3 times as much as 
> heartbeat?
> 
> 
> public HeaderExchangeServer(Server server) {
>if (server == null) {
>throw new IllegalArgumentException("server == null");
>}
>this.server = server;
>this.heartbeat = server.getUrl().getParameter(Constants.HEARTBEAT_KEY, 0);
>this.heartbeatTimeout = 
> server.getUrl().getParameter(Constants.HEARTBEAT_TIMEOUT_KEY, heartbeat * 3);
>if (heartbeatTimeout < heartbeat * 2) {
>throw new IllegalStateException("heartbeatTimeout < heartbeatInterval 
> * 2");
>}
>startHeatbeatTimer();
> }

Re: Re: How to add Apache license head to the files of hessian-lite sub project

[Kimm King]

In my opion, it's better to keep author info for respect.
Just think sometimes other guys copy your codes.



KimmKing(kimmk...@163.com)
 == In me the tiger sniffs the rose. ==

 
发件人： Wang Xin
发送时间： 2018-03-13 22:02
收件人： dev@dubbo.apache.org
主题： Re: How to add Apache license head to the files of hessian-lite sub project
Should the author info be removed?  @author Scott Ferguson
 
Xin Wang
lovep...@hotmail.com
 
 
 
在 2018年3月13日，下午7:50，Mark Thomas > 写道：
 
On 13/03/18 06:03, Ian Luo wrote:
+1 to keep original license info since it’s Apache License 1.0.
 
Mentors, would you mind to guide us on this particular problem?
 
Leave the ALv1.1 headers (with the copyright) in place.
 
The text from section 3 should appear in the NOTICE file.
 
Mark
 
 
 
Thanks,
-Ian.
 
On 12 Mar 2018, at 7:02 PM, Kimm King 
> wrote:
 
I think keeping the notice is awesome.
 
 
 
KimmKing(kimmk...@163.com)
== In me the tiger sniffs the rose. ==
 
 
发件人： Wang Xin
发送时间： 2018-03-12 18:01
收件人： dev@dubbo.apache.org
主题： How to add Apache license head to the files of hessian-lite sub project
Hi,all
 Now I’m adding Apache license head to the Dubbo project.  I find that ,the 
hessian-lite sub project is totally  copied from hessian project 
(http://hessian.caucho.com/) , it’s package is modified and maintained here.
The hessian project complies with Apache license 1.1. The license head in each 
file is as the following:
What should I do with it?
 
/*
* Copyright (c) 2001-2004 Caucho Technology, Inc.  All rights reserved.
*
* The Apache Software License, Version 1.1
*
* Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that the following conditions
* are met:
*
* 1. Redistributions of source code must retain the above copyright
*notice, this list of conditions and the following disclaimer.
*
* 2. Redistributions in binary form must reproduce the above copyright
*notice, this list of conditions and the following disclaimer in
*the documentation and/or other materials provided with the
*distribution.
*
* 3. The end-user documentation included with the redistribution, if
*any, must include the following acknowlegement:
*   "This product includes software developed by the
*Caucho Technology (http://www.caucho.com/)."
*Alternately, this acknowlegement may appear in the software itself,
*if and wherever such third-party acknowlegements normally appear.
*
* 4. The names "Burlap", "Resin", and "Caucho" must not be used to
*endorse or promote products derived from this software without prior
*written permission. For written permission, please contact
*i...@caucho.com.
*
* 5. Products derived from this software may not be called "Resin"
*nor may "Resin" appear in their names without prior written
*permission of Caucho Technology.
*
* THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED
* WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
* OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
* DISCLAIMED.  IN NO EVENT SHALL CAUCHO TECHNOLOGY OR ITS CONTRIBUTORS
* BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY,
* OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT
* OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
* BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
* WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE
* OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN
* IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
*
* @author Scott Ferguson
*/
 
 
Xin Wang
lovep...@hotmail.com
 
 
 
 
 
 

Re: How to add Apache license head to the files of hessian-lite sub project

[Justin Mclean]

Hi,

> The text from section 3 should appear in the NOTICE file.

It seems to be a combination of a BSD license and Apache which is slightly 
confusing. IMO nothing needs to go in NOTICE but we probably need to look into 
it in a little more detail.

Thanks,
Justin

Re: Suggestions on the organizational form of the code repository after confirming the submission of the dubbo code to apache

[jun liu]

> Are you looking to continue to use github as the primary repository
> location, or switch to our internal git? I'd recommend github since you're
> already there.

+1 stick to github, just transfer to github/apache after the IP Clearance sort 
of things

>  For the git repos not moving over, is there any reason they
> would not come over?

Maybe zonghai worries about too many repos, and demo doesn't seems to be as 
important as the core or extensions.
What about we merge all side projects(demos or extensions) into one repo after 
transfer？Otherwise, there will be two much repos: dubbo-ops, dubbo-docs, 
dubbo-jsonrpc and other extensions or demos that may come up in future.

> On 13 Mar 2018, at 11:39 PM, John D. Ament  wrote:
> 
> All repositories coming in for dubbo will be prefixed as "incubator-dubbo",
> this is a requirement.
> 
> Are you looking to continue to use github as the primary repository
> location, or switch to our internal git? I'd recommend github since you're
> already there.  For the git repos not moving over, is there any reason they
> would not come over?
> 
> John
> 
> On Tue, Mar 13, 2018 at 11:30 AM zonghai shang 
> wrote:
> 
>> Sorry, E-mail support for forms is not friendly, Here is a picture of the
>> project structure change.
>> 
>> Here are directory of project structure changes:
>> 
>> 
>> Here are main changes:
>> 
>> 
>> 
>>   1. dubbo/dubbo.github.io renamed to apache/dubbo-website after import
>>   to apache.
>>   2. dubbo/dubbo-spring-boot-project renamed to apache/dubbo-spring-boot
>>   after import to apache.
>>   3. dubbo/dubbo-rpc-jsonrpc renamed to apache/dubbo-jsonrpc after
>>   import to apache.
>>   4. dubbo/dubbo-feature-test rename to apache/dubbo-feature-test after
>>   import to apache.
>>   5. The remaining submissions to the apache project rename the prefix
>>   dubbo to apache.
>> 
>> Reasons for suggesting structural adjustment:
>>   1. I suggest adjusting because the naming is clearer and easier to
>> understand.
>>   2. Refer to existing apache projects apache/commons-io,
>> apache/commons-lang, apache/commons-math and so on.
>> 
>> Welcome everyone to make suggestions.
>> 

Re: Suggestions on the organizational form of the code repository after confirming the submission of the dubbo code to apache

[Ian Luo]

To summarize, we will transfer dubbo and its relevant side projects into 
github.com/apache  with the prefix 'incubator-dubbo-
', and will start IP clearance as early as possible even though this work 
doesn’t block the transition.


Regards,
-Ian.


> On 14 Mar 2018, at 1:26 PM, Justin Mclean  wrote:
> 
> Hi,
> 
>> 1.  Can we put the project at 
>> https://github.com/apache/ ？
>> 
>>for example:
>>a.  alibaba/dubbo move to https://github.com/apache/incubator-dubbo
>>b.  dubbo/dubbo.github.io move to 
>> https://github.com/apache/incubator-dubbo-website
>>c.  dubbo/dubbo-spring-boot-project move to 
>> https://github.com/apache/incubator-dubbo-spring-boot.
>>d.  dubbo/dubbo-rpc-jsonrpc move to 
>> https://github.com/apache/incubator-dubbo-jsonrpc.
>>e.  dubbo/dubbo-feature-test move to 
>> https://github.com/apache/incubator-dubbo-feature-test .
> 
> Looks good to me. Getting the website published from that repo may take a 
> little work.
> 
>>2.  If the IP clearance( and some other tasks, eg  contributors cla) only 
>> really needs to be sorted out before graduation， we may work on it there not 
>> current existing github repo (https://github.com/alibaba/dubbo).
> 
> The earlier these are sorted out the better IMO, so I wouldn’t put it off 
> until just before graduation, I would get started on it now, it may talk some 
> time to sort everything out.
> 
> Thanks,
> Justin

Re: Suggestions on the organizational form of the code repository after confirming the submission of the dubbo code to apache

[Huxing Zhang]

Hi Justin,

On Wed, Mar 14, 2018 at 10:39 AM, Justin Mclean
 wrote:
> Hi,
>
>>> Are you looking to continue to use github as the primary repository
>>> location, or switch to our internal git? I'd recommend github since you're
>>> already there.
>>
>> +1 stick to github, just transfer to github/apache after the IP Clearance 
>> sort of things
>
> With my mentors hat on I think it would be better to transfer the code to the 
> ASF repos and work on it there. The IP clearance only really needs to be 
> sorted out before graduation.

There was some misunderstanding in the incubating process. I thought
the IP clearance must be done before moving to ASF repo. So did some
of the committers.

Now that you've pointed out, I think we should move the repo as soon
as possible.

>
> Thanks,
> Justin



-- 
Best Regards！
Huxing

Re: Suggestions on the organizational form of the code repository after confirming the submission of the dubbo code to apache

[Huxing Zhang]

Filed a INFRA ticket:
https://issues.apache.org/jira/projects/INFRA/issues/INFRA-16182

On Wed, Mar 14, 2018 at 1:46 PM, Ian Luo  wrote:
> To summarize, we will transfer dubbo and its relevant side projects into 
> github.com/apache  with the prefix 'incubator-dubbo-
> ', and will start IP clearance as early as possible even though this work 
> doesn’t block the transition.
>
>
> Regards,
> -Ian.
>
>
>> On 14 Mar 2018, at 1:26 PM, Justin Mclean  wrote:
>>
>> Hi,
>>
>>> 1.  Can we put the project at 
>>> https://github.com/apache/ ？
>>>
>>>for example:
>>>a.  alibaba/dubbo move to https://github.com/apache/incubator-dubbo
>>>b.  dubbo/dubbo.github.io move to 
>>> https://github.com/apache/incubator-dubbo-website
>>>c.  dubbo/dubbo-spring-boot-project move to 
>>> https://github.com/apache/incubator-dubbo-spring-boot.
>>>d.  dubbo/dubbo-rpc-jsonrpc move to 
>>> https://github.com/apache/incubator-dubbo-jsonrpc.
>>>e.  dubbo/dubbo-feature-test move to 
>>> https://github.com/apache/incubator-dubbo-feature-test .
>>
>> Looks good to me. Getting the website published from that repo may take a 
>> little work.
>>
>>>2.  If the IP clearance( and some other tasks, eg  contributors cla) 
>>> only really needs to be sorted out before graduation， we may work on it 
>>> there not current existing github repo (https://github.com/alibaba/dubbo).
>>
>> The earlier these are sorted out the better IMO, so I wouldn’t put it off 
>> until just before graduation, I would get started on it now, it may talk 
>> some time to sort everything out.
>>
>> Thanks,
>> Justin
>



-- 
Best Regards！
Huxing

Re: Suggestions on the organizational form of the code repository after confirming the submission of the dubbo code to apache

[Von Gosling]

Hi,

I really suggest we could be better to transfer the code to the ASF at the 
first stage. But one complicated point around my hat, how could we arrange the 
repositories in the Apache Git Repository? if we hope to keep the same release 
pace with so many repositories.

Best Regards,
Von Gosling


> 在 2018年3月14日，10:39，Justin Mclean  写道：
> 
> With my mentors

Re: Suggestions on the organizational form of the code repository after confirming the submission of the dubbo code to apache

[Justin Mclean]

Hi,

>> Are you looking to continue to use github as the primary repository
>> location, or switch to our internal git? I'd recommend github since you're
>> already there.
> 
> +1 stick to github, just transfer to github/apache after the IP Clearance 
> sort of things

With my mentors hat on I think it would be better to transfer the code to the 
ASF repos and work on it there. The IP clearance only really needs to be sorted 
out before graduation.

Thanks,
Justin

Re: How to add Apache license head to the files of hessian-lite sub project

[Justin Mclean]

Hi,

> Then we need to rollback what we made in hessian-lite module and keep the 
> original license/author info as is. As Justin suggested, pls. also cross 
> check LICENSE file.

Don’t be too concern about what goes in LICENCE and NOTICE right now we can fix 
that up before the first release.

Thanks,
Justin

Re: [alibaba/dubbo] [BUG][2.5.10] Implementation-Version is incorrect (#1466)

[Jun Liu]

This has been changed since 2.5.9, does this change has some side effects on 
your project?

> On 14 Mar 2018, at 11:25 AM, Jason Song  wrote:
> 
> The manifest info of the newly released 2.5.10 is incorrect, which causes 
> com.alibaba.dubbo.common.Version#getVersion() returns the wrong version - 
> 2.0.1.
> 
> The following is the manifest of 2.5.10:
> 
> Manifest-Version: 1.0
> Implementation-Vendor: The Dubbo Project
> Implementation-Title: Dubbo
> Implementation-Version: 2.0.1
> Implementation-Vendor-Id: com.alibaba
> Built-By: ken.lj
> Build-Jdk: 1.7.0_80
> Specification-Vendor: The Dubbo Project
> Specification-Title: Dubbo
> Created-By: Apache Maven 3.1.1
> Specification-Version: 2.0.0
> Archiver-Version: Plexus Archiver
> Here is the manifest of 2.5.8, which is correct:
> 
> Manifest-Version: 1.0
> Implementation-Vendor: Alibaba
> Implementation-Title: Dubbo
> Implementation-Version: 2.5.8
> Implementation-Vendor-Id: com.alibaba
> Built-By: ken.lj
> Build-Jdk: 1.6.0_32
> Specification-Vendor: Alibaba
> Specification-Title: Dubbo
> Created-By: Apache Maven 3.1.1
> Specification-Version: 2.5.8
> Archiver-Version: Plexus Archiver
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub 
> , or mute the thread 
> .
> 

Re: [alibaba/dubbo] [BUG][2.5.10] Implementation-Version is incorrect (#1466)

[ss宋顺]

Hi Jun,

We have integrated dubbo with our tracing system, which will include dubbo 
version in each rpc call event.

The version information is one of the key diagnosis information when some 
service meets something wrong.

So yes, this change does have some side effects. Not on my project but on many 
services using our sdk.


Thanks!
Jason




On 14/03/2018, 14:27, "Jun Liu"  wrote:

>This has been changed since 2.5.9, does this change has some side effects on 
>your project?
>
>> On 14 Mar 2018, at 11:25 AM, Jason Song  wrote:
>> 
>> The manifest info of the newly released 2.5.10 is incorrect, which causes 
>> com.alibaba.dubbo.common.Version#getVersion() returns the wrong version - 
>> 2.0.1.
>> 
>> The following is the manifest of 2.5.10:
>> 
>> Manifest-Version: 1.0
>> Implementation-Vendor: The Dubbo Project
>> Implementation-Title: Dubbo
>> Implementation-Version: 2.0.1
>> Implementation-Vendor-Id: com.alibaba
>> Built-By: ken.lj
>> Build-Jdk: 1.7.0_80
>> Specification-Vendor: The Dubbo Project
>> Specification-Title: Dubbo
>> Created-By: Apache Maven 3.1.1
>> Specification-Version: 2.0.0
>> Archiver-Version: Plexus Archiver
>> Here is the manifest of 2.5.8, which is correct:
>> 
>> Manifest-Version: 1.0
>> Implementation-Vendor: Alibaba
>> Implementation-Title: Dubbo
>> Implementation-Version: 2.5.8
>> Implementation-Vendor-Id: com.alibaba
>> Built-By: ken.lj
>> Build-Jdk: 1.6.0_32
>> Specification-Vendor: Alibaba
>> Specification-Title: Dubbo
>> Created-By: Apache Maven 3.1.1
>> Specification-Version: 2.5.8
>> Archiver-Version: Plexus Archiver
>> —
>> You are receiving this because you are subscribed to this thread.
>> Reply to this email directly, view it on GitHub 
>> , or mute the thread 
>> .
>> 
>