Hi Team:
In servicecomb-java-chassis, when calling RetryLoadBalancer#chooseServer,
the method will call LoadBalancer#chooseServer and 17 duplicate logs may be
printed when all of the following happen:
1. There are 1 or more ServiceCombServer after getting servers from local
context;
2. There
+1
-- Original --
From: Xiaoliang Tian https://dist.apache.org/repos/dist/dev/servicecomb/servicecomb-mesher/1.6.3/rc-02/
Release Tag :
https://github.com/apache/servicecomb-mesher/tree/v1.6.3
Release CommitID:
+1
--Original--
From:"victor chan"mailto:xiaoliang.t...@gmail.com]
: 2019??9??3?? 19:27
??: dev https://dist.apache.org/repos/dist/dev/servicecomb/servicecomb-mesher/1.6.3/rc-01/
Release Tag :
Hi Team,
In java-chasis-dependencies, some dependency versions are set as properties
while others not. As DM, it is not very clear to show version informations and
also not convenient for version updating.
In spring-boot-dependencies and spring-cloud-dependencies, ALL version
informations
Hi Team,
Currently, ServiceComb Java-Chasis does not support websocket and some users
are confused about that.
WebSocket, as a communications protocol, can be used in many situations and
websocket is supported by many other frameworks.
So should we support websocket in ServiceComb
+1.
Most open source project users are more familiar with issue module than with
JIRA.
Best,
Ang Li
-- --
??: "yhs0092";
: 2019??8??6??(??) 9:07
??: "dev@servicecomb.apache.org";
: Re: [DISSCUSSIOIN] Adding 'Issues'
Hey Guys,
I found a problem using
org.apache.servicecomb.foundation.common.utils.BeanUtils#getImplClassFromBean.
If the @param bean is a cgLib proxy subclass bean, the getImplClassFromBean
method will return null instead of super class which is expected. To make the
issure more clearly, I
