do you mean microservice instance provide RESTful api
and a standalone instance to provide UI?
seems like another governance entry..
bismy 于2019年3月6日周三 下午4:13写道：
> I have an general idea to do this:
>
>
> 1. We do not need to create a new port for this feature, and share the
> microservice
+1 for upgrading the spring-boot version both 2.x and 1.5.x.
Willem Jiang
Twitter: willemjiang
Weibo: 姜宁willem
On Wed, Mar 6, 2019 at 4:22 PM bismy wrote:
>
> Now java chassis depend on spring boot 2 2.0.0.RELEASE, this version is quite
> old fashioned. Although users can use dependency manage
+1
bismy 于2019年3月6日周三 下午4:22写道：
> Now java chassis depend on spring boot 2 2.0.0.RELEASE, this version is
> quite old fashioned. Although users can use dependency management to use
> other versions, but sometimes it is difficult to do so. Spring boot 2
> changed rapidly and many compatible probl
+1 Please merge my PR https://github.com/apache/servicecomb-pack/pull/420
before this
coolbeevip
BOCO
> 在 2019年3月6日，下午2:29，Willem Jiang 写道：
>
> It's time for us to think about ServiceComb release now.
>
> As usual, we will release ServiceComb Java-Chassis 1.2.0, Se
Now java chassis depend on spring boot 2 2.0.0.RELEASE, this version is quite
old fashioned. Although users can use dependency management to use other
versions, but sometimes it is difficult to do so. Spring boot 2 changed rapidly
and many compatible problems with spring 5 version.
So I sugges
I have an general idea to do this:
1. We do not need to create a new port for this feature, and share the
microservice port. It has same security constraints like REST api.
2. We can provide both ui and REST api for this feature. Provided we need to
easily access the ui from edge service(Is th
+1 we have many important modifications since last release
-- --
??: "zzzwjm";
: 2019??3??6??(??) 2:56
??: "dev";
: Re: Release of ServiceComb
ok
Willem Jiang ??2019??3??6?? 2:53??
> It's time for us to thin
