[jira] [Closed] (SCB-1033) Update license for Service-Center
[ https://issues.apache.org/jira/browse/SCB-1033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yang Bo closed SCB-1033. Resolution: Later The 1.1.0 release still uses glide for package management. Will revisit this issue once we migrate to go mod. > Update license for Service-Center > - > > Key: SCB-1033 > URL: https://issues.apache.org/jira/browse/SCB-1033 > Project: Apache ServiceComb > Issue Type: Task > Components: Service-Center >Affects Versions: service-center-1.1.0 >Reporter: Yang Bo >Assignee: Yang Bo >Priority: Major > Fix For: service-center-1.1.0 > > > Update license for Service-Center -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-1035) Update third party licenses for java-chassis
Yang Bo created SCB-1035: Summary: Update third party licenses for java-chassis Key: SCB-1035 URL: https://issues.apache.org/jira/browse/SCB-1035 Project: Apache ServiceComb Issue Type: Task Components: Java-Chassis Affects Versions: java-chassis-1.1.0 Reporter: Yang Bo Assignee: Yang Bo Fix For: java-chassis-1.1.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SCB-986) ServerInstances can be cached in spring-boot2-starter-discovery
[ https://issues.apache.org/jira/browse/SCB-986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yang Bo resolved SCB-986. - Resolution: Fixed Fix Version/s: java-chassis-1.1.0 done > ServerInstances can be cached in spring-boot2-starter-discovery > --- > > Key: SCB-986 > URL: https://issues.apache.org/jira/browse/SCB-986 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Java-Chassis >Affects Versions: java-chassis-1.1.0 >Reporter: Yang Bo >Assignee: Yang Bo >Priority: Minor > Fix For: java-chassis-1.1.0 > > > ServerInstances can be cached in spring-boot2-starter-discovery and > spring-boot-starter-discovery -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (SCB-985) Add springboot2-starter-discovery
[ https://issues.apache.org/jira/browse/SCB-985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yang Bo closed SCB-985. --- > Add springboot2-starter-discovery > - > > Key: SCB-985 > URL: https://issues.apache.org/jira/browse/SCB-985 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Java-Chassis >Reporter: Yang Bo >Assignee: Yang Bo >Priority: Major > Fix For: java-chassis-1.1.0 > > > Copied springboot-starter-discovery to spritnboot2. Removed test code and > updated some spring-boot and spring-cloud versions. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SCB-985) Add springboot2-starter-discovery
[ https://issues.apache.org/jira/browse/SCB-985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yang Bo resolved SCB-985. - Resolution: Fixed > Add springboot2-starter-discovery > - > > Key: SCB-985 > URL: https://issues.apache.org/jira/browse/SCB-985 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Java-Chassis >Reporter: Yang Bo >Assignee: Yang Bo >Priority: Major > Fix For: java-chassis-1.1.0 > > > Copied springboot-starter-discovery to spritnboot2. Removed test code and > updated some spring-boot and spring-cloud versions. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-986) ServerInstances can be cached in spring-boot2-starter-discovery
Yang Bo created SCB-986: --- Summary: ServerInstances can be cached in spring-boot2-starter-discovery Key: SCB-986 URL: https://issues.apache.org/jira/browse/SCB-986 Project: Apache ServiceComb Issue Type: Improvement Components: Java-Chassis Affects Versions: java-chassis-1.1.0 Reporter: Yang Bo Assignee: Yang Bo ServerInstances can be cached in spring-boot2-starter-discovery and spring-boot-starter-discovery -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-985) Add springboot2-starter-discovery
Yang Bo created SCB-985: --- Summary: Add springboot2-starter-discovery Key: SCB-985 URL: https://issues.apache.org/jira/browse/SCB-985 Project: Apache ServiceComb Issue Type: Improvement Components: Java-Chassis Affects Versions: java-chassis-1.1.0 Reporter: Yang Bo Assignee: Yang Bo Copied springboot-starter-discovery to spritnboot2. Removed test code and updated some spring-boot and spring-cloud versions. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SCB-871) Add schema source code editor in Schema Test module
[ https://issues.apache.org/jira/browse/SCB-871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16602732#comment-16602732 ] Yang Bo commented on SCB-871: - Reference: [http://editor.swagger.io/#/] It seems not neccessary/impossible to edit the schema source, just displaying it is enough. [~little-cui] > Add schema source code editor in Schema Test module > --- > > Key: SCB-871 > URL: https://issues.apache.org/jira/browse/SCB-871 > Project: Apache ServiceComb > Issue Type: New Feature > Components: Service-Center >Reporter: little-cui >Assignee: xiaoyimei >Priority: Major > Fix For: service-center-1.1.0 > > > Just like swagger.io, developer can edit the source code in Schema Test dialog -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-822) Update LICENSE/NOTICE for saga
Yang Bo created SCB-822: --- Summary: Update LICENSE/NOTICE for saga Key: SCB-822 URL: https://issues.apache.org/jira/browse/SCB-822 Project: Apache ServiceComb Issue Type: Bug Components: Saga Affects Versions: saga-0.3.0 Reporter: Yang Bo Assignee: Yang Bo Fix For: saga-0.3.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-821) Add missing dependencyManagement for omega-transport-feign
Yang Bo created SCB-821: --- Summary: Add missing dependencyManagement for omega-transport-feign Key: SCB-821 URL: https://issues.apache.org/jira/browse/SCB-821 Project: Apache ServiceComb Issue Type: Bug Components: Saga Affects Versions: saga-0.3.0 Reporter: Yang Bo Assignee: Yang Bo Fix For: saga-0.3.0 Project failed to build with -Prelease due to missing version information of omega-transport-feign. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-771) Update LICENSE/NOTICE for Service-Center 1.0.0 release
Yang Bo created SCB-771: --- Summary: Update LICENSE/NOTICE for Service-Center 1.0.0 release Key: SCB-771 URL: https://issues.apache.org/jira/browse/SCB-771 Project: Apache ServiceComb Issue Type: Improvement Components: Service-Center Affects Versions: service-center-1.0.0 Reporter: Yang Bo Assignee: Yang Bo Fix For: service-center-1.0.0 Add missing dependencies in LICENSE for binary release. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SCB-575) Publish the Java doc of ServiceComb projects
[ https://issues.apache.org/jira/browse/SCB-575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16550102#comment-16550102 ] Yang Bo commented on SCB-575: - The PR is rejected. We might need a better way to include the javadoc into the website. Perhaps something like the chassis gitbook, host the javadoc in a separate server(not the jekyel server the main site used) and link it in the site. > Publish the Java doc of ServiceComb projects > > > Key: SCB-575 > URL: https://issues.apache.org/jira/browse/SCB-575 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Java-Chassis, Saga >Reporter: Willem Jiang >Assignee: Yang Bo >Priority: Major > Fix For: java-chassis-1.0.0, saga-0.3.0 > > > We should generate the API document and publish it to the website. > * Aggregate the java doc > * Submit the generated pages to ServiceComb website. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SCB-750) Dependency management is incomplete in Saga and Java-Chassis
[ https://issues.apache.org/jira/browse/SCB-750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yang Bo resolved SCB-750. - Resolution: Fixed > Dependency management is incomplete in Saga and Java-Chassis > > > Key: SCB-750 > URL: https://issues.apache.org/jira/browse/SCB-750 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Java-Chassis, Saga >Reporter: Yang Bo >Assignee: Yang Bo >Priority: Minor > Fix For: java-chassis-1.0.0, saga-0.3.0 > > > Dependency management is incomplete in Saga and Java-Chassis -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SCB-748) ServiceComb engine resource optimize
[ https://issues.apache.org/jira/browse/SCB-748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16548987#comment-16548987 ] Yang Bo commented on SCB-748: - Jackson now has some protobuf3 support. https://github.com/HubSpot/jackson-datatype-protobuf/blob/jackson29-proto3/README.md#protobuf-3-support > ServiceComb engine resource optimize > > > Key: SCB-748 > URL: https://issues.apache.org/jira/browse/SCB-748 > Project: Apache ServiceComb > Issue Type: Task > Components: Java-Chassis >Reporter: wujimin >Assignee: wujimin >Priority: Major > > to support protobuf codec not coupled with business logic, we must create > classloader for each microserviceId(app/microservice/version), and create > classes in it dynamiclly. > that makes logic very complex, because must support generic and recursive > reference. > and in edge, create too many classes, will cause jvm meta area overflow > so we will change invocation mechanism from strong type to weak type: > * protobuf codec based on IDL not model class, maybe will switch from > protoStuff to jackson, (protoStuff not support IDL, jackson support idl but > not support protobuf V3) > * delete all mechanism related to dynamic class creation > * invocation not unify to RPC argument, but unify to HttpServletRequestEx -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-750) Dependency management is incomplete in Saga and Java-Chassis
Yang Bo created SCB-750: --- Summary: Dependency management is incomplete in Saga and Java-Chassis Key: SCB-750 URL: https://issues.apache.org/jira/browse/SCB-750 Project: Apache ServiceComb Issue Type: Improvement Components: Java-Chassis, Saga Reporter: Yang Bo Assignee: Yang Bo Fix For: java-chassis-1.0.0, saga-0.3.0 Dependency management is incomplete in Saga and Java-Chassis -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-666) Test failure on system that have rotate option set in /etc/resolv.conf
Yang Bo created SCB-666: --- Summary: Test failure on system that have rotate option set in /etc/resolv.conf Key: SCB-666 URL: https://issues.apache.org/jira/browse/SCB-666 Project: Apache ServiceComb Issue Type: Bug Components: Java-Chassis Reporter: Yang Bo Assignee: Yang Bo Fix For: Java-chassis-1.0.0 Test failure on system that have rotate option set in /etc/resolv.conf Failed tests: TestAbstractClientPool.create:83 expected:<...rue,"rotateServers":[fals]e}> but was:<...rue,"rotateServers":[tru]e}> Vertx read /etc/resolv.conf and set the option according to the rotate configuration. Need to fix the test case, only check the bits that's are specifically set. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-381) Fix foudation-vertx UT failure on linux
[
https://issues.apache.org/jira/browse/SCB-381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yang Bo updated SCB-381:
Fix Version/s: (was: java-chassis-1.0.0-m2)
Java-chassis-1.0.0
> Fix foudation-vertx UT failure on linux
> ---
>
> Key: SCB-381
> URL: https://issues.apache.org/jira/browse/SCB-381
> Project: Apache ServiceComb
> Issue Type: Bug
> Components: Java-Chassis
>Reporter: Yang Bo
>Assignee: wujimin
>Priority: Major
> Fix For: Java-chassis-1.0.0
>
> Attachments: image-2018-04-23-10-55-12-897.png
>
>
> The foudation-vertx's UT would fail on some linux platforms.
> Environment:
> 1.
> OS: Ubuntu 16.04.4 LTS 64 bit
> JDK: jdk1.8.0_151 64 bit
> 2.
> OS: Centos 7 64 bit
> JDK: jdk1.8.0_161 64 bit
> Errors:
> TestAbstractTcpClientPoolFactory.createClientPool:45 » NullPointer
> TestTcpClientConnection.send_inWorkingStatus:103 NullPointer
> Here are the stack trace that we got:
> Running
> org.apache.servicecomb.foundation.vertx.client.tcp.TestAbstractTcpClientPoolFactory
> {code:java}
> java.lang.NullPointerException
> at io.vertx.core.net.TCPSSLOptions.equals(TCPSSLOptions.java:685)
> at
> io.vertx.core.net.ClientOptionsBase.equals(ClientOptionsBase.java:363)
> at
> io.vertx.core.net.NetClientOptions.equals(NetClientOptions.java:356)
> at
> mockit.internal.expectations.argumentMatching.EqualityMatcher.areEqualWhenNonNull(EqualityMatcher.java:49)
> at
> mockit.internal.expectations.invocation.ArgumentValuesAndMatchers.isNotEqual(ArgumentValuesAndMatchers.java:79)
> at
> mockit.internal.expectations.invocation.ArgumentValuesAndMatchers.areEqual(ArgumentValuesAndMatchers.java:64)
> at
> mockit.internal.expectations.invocation.ArgumentValuesAndMatchersWithoutVarargs.isMatch(ArgumentValuesAndMatchersWithoutVarargs.java:23)
> at
> mockit.internal.expectations.invocation.InvocationArguments.isMatch(InvocationArguments.java:71)
> at
> mockit.internal.expectations.PhasedExecutionState.findNotStrictExpectation(PhasedExecutionState.java:210)
> at
> mockit.internal.expectations.ReplayPhase.handleInvocation(ReplayPhase.java:63)
> at
> mockit.internal.expectations.RecordAndReplayExecution.recordOrReplay(RecordAndReplayExecution.java:198)
> at io.vertx.core.$Impl_Vertx.createNetClient(Unknown Source)
> at
> org.apache.servicecomb.foundation.vertx.client.tcp.NetClientWrapper.(NetClientWrapper.java:42)
> at
> org.apache.servicecomb.foundation.vertx.client.tcp.AbstractTcpClientPoolFactory.createClientPool(AbstractTcpClientPoolFactory.java:39)
> at
> org.apache.servicecomb.foundation.vertx.client.tcp.TestAbstractTcpClientPoolFactory.createClientPool(TestAbstractTcpClientPoolFactory.java:48)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> mockit.integration.junit4.internal.JUnit4TestRunnerDecorator.executeTestMethod(JUnit4TestRunnerDecorator.java:162)
> at
> mockit.integration.junit4.internal.JUnit4TestRunnerDecorator.invokeExplosively(JUnit4TestRunnerDecorator.java:71)
> at
> mockit.integration.junit4.internal.MockFrameworkMethod.invokeExplosively(MockFrameworkMethod.java:37)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at
>
[jira] [Reopened] (SCB-381) Fix foudation-vertx UT failure on linux
[
https://issues.apache.org/jira/browse/SCB-381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yang Bo reopened SCB-381:
-
Assignee: wujimin (was: Willem Jiang)
Build still fails with the following test error on Centos 7
Tests in error:
TestHttpClientPoolFactory.createClientPool:37 » NullPointer
TestAbstractTcpClientPoolFactory.createClientPool:37 » NullPointer
TestTcpClientConnectionPool.setup:38 » NullPointer
> Fix foudation-vertx UT failure on linux
> ---
>
> Key: SCB-381
> URL: https://issues.apache.org/jira/browse/SCB-381
> Project: Apache ServiceComb
> Issue Type: Bug
> Components: Java-Chassis
>Reporter: Yang Bo
>Assignee: wujimin
>Priority: Major
> Fix For: java-chassis-1.0.0-m2
>
> Attachments: image-2018-04-23-10-55-12-897.png
>
>
> The foudation-vertx's UT would fail on some linux platforms.
> Environment:
> 1.
> OS: Ubuntu 16.04.4 LTS 64 bit
> JDK: jdk1.8.0_151 64 bit
> 2.
> OS: Centos 7 64 bit
> JDK: jdk1.8.0_161 64 bit
> Errors:
> TestAbstractTcpClientPoolFactory.createClientPool:45 » NullPointer
> TestTcpClientConnection.send_inWorkingStatus:103 NullPointer
> Here are the stack trace that we got:
> Running
> org.apache.servicecomb.foundation.vertx.client.tcp.TestAbstractTcpClientPoolFactory
> {code:java}
> java.lang.NullPointerException
> at io.vertx.core.net.TCPSSLOptions.equals(TCPSSLOptions.java:685)
> at
> io.vertx.core.net.ClientOptionsBase.equals(ClientOptionsBase.java:363)
> at
> io.vertx.core.net.NetClientOptions.equals(NetClientOptions.java:356)
> at
> mockit.internal.expectations.argumentMatching.EqualityMatcher.areEqualWhenNonNull(EqualityMatcher.java:49)
> at
> mockit.internal.expectations.invocation.ArgumentValuesAndMatchers.isNotEqual(ArgumentValuesAndMatchers.java:79)
> at
> mockit.internal.expectations.invocation.ArgumentValuesAndMatchers.areEqual(ArgumentValuesAndMatchers.java:64)
> at
> mockit.internal.expectations.invocation.ArgumentValuesAndMatchersWithoutVarargs.isMatch(ArgumentValuesAndMatchersWithoutVarargs.java:23)
> at
> mockit.internal.expectations.invocation.InvocationArguments.isMatch(InvocationArguments.java:71)
> at
> mockit.internal.expectations.PhasedExecutionState.findNotStrictExpectation(PhasedExecutionState.java:210)
> at
> mockit.internal.expectations.ReplayPhase.handleInvocation(ReplayPhase.java:63)
> at
> mockit.internal.expectations.RecordAndReplayExecution.recordOrReplay(RecordAndReplayExecution.java:198)
> at io.vertx.core.$Impl_Vertx.createNetClient(Unknown Source)
> at
> org.apache.servicecomb.foundation.vertx.client.tcp.NetClientWrapper.(NetClientWrapper.java:42)
> at
> org.apache.servicecomb.foundation.vertx.client.tcp.AbstractTcpClientPoolFactory.createClientPool(AbstractTcpClientPoolFactory.java:39)
> at
> org.apache.servicecomb.foundation.vertx.client.tcp.TestAbstractTcpClientPoolFactory.createClientPool(TestAbstractTcpClientPoolFactory.java:48)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> mockit.integration.junit4.internal.JUnit4TestRunnerDecorator.executeTestMethod(JUnit4TestRunnerDecorator.java:162)
> at
> mockit.integration.junit4.internal.JUnit4TestRunnerDecorator.invokeExplosively(JUnit4TestRunnerDecorator.java:71)
> at
> mockit.integration.junit4.internal.MockFrameworkMethod.invokeExplosively(MockFrameworkMethod.java:37)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at
[jira] [Commented] (SCB-475) 新版的release编译包啥时候放出来啊？
[ https://issues.apache.org/jira/browse/SCB-475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16505824#comment-16505824 ] Yang Bo commented on SCB-475: - [~njiang] Could you please resolve this issue as the downloading guide for all 3 components have added. > 新版的release编译包啥时候放出来啊？ > - > > Key: SCB-475 > URL: https://issues.apache.org/jira/browse/SCB-475 > Project: Apache ServiceComb > Issue Type: Wish >Reporter: geon >Assignee: Yang Bo >Priority: Major > > 新版的release编译包啥时候放出来啊？ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-647) Update LICENSE/NOTICE for release
Yang Bo created SCB-647: --- Summary: Update LICENSE/NOTICE for release Key: SCB-647 URL: https://issues.apache.org/jira/browse/SCB-647 Project: Apache ServiceComb Issue Type: Task Components: Java-Chassis, Saga, Service-Center Reporter: Yang Bo Assignee: Yang Bo Update the LICENSE/NOTICE for second release. java-chassis: 1.0.0-m2 service-center: 1.0.0-m2 saga: 0.2.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SCB-576) javassist License file need to be updated
[ https://issues.apache.org/jira/browse/SCB-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16494837#comment-16494837 ] Yang Bo commented on SCB-576: - Below is the license for javassist. It's ASLv2/lgpl dua licensed. We choose to use ASLv2 and thus it's OK that we list it under the ASLv2 list. https://github.com/jboss-javassist/javassist/blob/rel_3_18_1_ga/License.html > javassist License file need to be updated > - > > Key: SCB-576 > URL: https://issues.apache.org/jira/browse/SCB-576 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Java-Chassis >Reporter: Willem Jiang >Assignee: Yang Bo >Priority: Minor > Fix For: java-chassis-1.0.0-m2 > > > Since Java Chassis has long history, even the License is changed into ASL, > the license file not the normal one we use. So we still need to add the > License file for it. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SCB-13) refactor service registry module
[ https://issues.apache.org/jira/browse/SCB-13?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16477169#comment-16477169 ] Yang Bo commented on SCB-13: Perhaps we can just close it. > refactor service registry module > > > Key: SCB-13 > URL: https://issues.apache.org/jira/browse/SCB-13 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Java-Chassis >Reporter: Eric Lee >Priority: Major > Labels: service-orchestration > Fix For: java-chassis-1.0.0-m2 > > > Currently, the service registry module in Java Chassis has the following > problems: > - Low level components access high level components frequently. The cyclic > relationships make the implementation complicated and introduce some > redundant access points. > - Low level components should be stateless to be reused by high level > components. Introducing state into low level components makes it relies > heavily on the high level components, causing cyclic relationships. > - Hard to integrate with third-party framework. It does not provide a > standalone client with cache capability inside. It also requires the > configurations should be loaded from dynamic properties. > Details: > [http://servicecomb.io/docs/service-registry-refactor-proposal/|http://servicecomb.io/docs/service-registry-refactor-proposal/] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-13) refactor service registry module
[ https://issues.apache.org/jira/browse/SCB-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yang Bo updated SCB-13: --- Fix Version/s: java-chassis-1.0.0-m2 > refactor service registry module > > > Key: SCB-13 > URL: https://issues.apache.org/jira/browse/SCB-13 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Java-Chassis >Reporter: Eric Lee >Priority: Major > Labels: service-orchestration > Fix For: java-chassis-1.0.0-m2 > > > Currently, the service registry module in Java Chassis has the following > problems: > - Low level components access high level components frequently. The cyclic > relationships make the implementation complicated and introduce some > redundant access points. > - Low level components should be stateless to be reused by high level > components. Introducing state into low level components makes it relies > heavily on the high level components, causing cyclic relationships. > - Hard to integrate with third-party framework. It does not provide a > standalone client with cache capability inside. It also requires the > configurations should be loaded from dynamic properties. > Details: > [http://servicecomb.io/docs/service-registry-refactor-proposal/|http://servicecomb.io/docs/service-registry-refactor-proposal/] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SCB-13) refactor service registry module
[ https://issues.apache.org/jira/browse/SCB-13?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16477119#comment-16477119 ] Yang Bo commented on SCB-13: [~wujimin] [~njiang] Could you please update or close this issue? > refactor service registry module > > > Key: SCB-13 > URL: https://issues.apache.org/jira/browse/SCB-13 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Java-Chassis >Reporter: Eric Lee >Priority: Major > Labels: service-orchestration > Fix For: java-chassis-1.0.0-m2 > > > Currently, the service registry module in Java Chassis has the following > problems: > - Low level components access high level components frequently. The cyclic > relationships make the implementation complicated and introduce some > redundant access points. > - Low level components should be stateless to be reused by high level > components. Introducing state into low level components makes it relies > heavily on the high level components, causing cyclic relationships. > - Hard to integrate with third-party framework. It does not provide a > standalone client with cache capability inside. It also requires the > configurations should be loaded from dynamic properties. > Details: > [http://servicecomb.io/docs/service-registry-refactor-proposal/|http://servicecomb.io/docs/service-registry-refactor-proposal/] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-14) transaction tracing with zipkin
[ https://issues.apache.org/jira/browse/SCB-14?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yang Bo updated SCB-14: --- Fix Version/s: saga-0.3.0 > transaction tracing with zipkin > --- > > Key: SCB-14 > URL: https://issues.apache.org/jira/browse/SCB-14 > Project: Apache ServiceComb > Issue Type: New Feature > Components: Saga >Reporter: Yin Xiang >Priority: Major > Fix For: saga-0.3.0 > > > integration with zipkin to providing timing info of transactions/compensations > *given* > configured saga with zipkin trace collector address and zipkin enabled > *when* > saga receives a request > *then* > tracing info is reported to zipkin trace collector -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SCB-15) service discovery with popular open source service registry
[ https://issues.apache.org/jira/browse/SCB-15?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16477114#comment-16477114 ] Yang Bo commented on SCB-15: [~njiang] Could you please update or close this issue? > service discovery with popular open source service registry > --- > > Key: SCB-15 > URL: https://issues.apache.org/jira/browse/SCB-15 > Project: Apache ServiceComb > Issue Type: New Feature > Components: Saga >Reporter: Yin Xiang >Priority: Major > > preferably consul -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SCB-16) service communication with MQ
[ https://issues.apache.org/jira/browse/SCB-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16477113#comment-16477113 ] Yang Bo commented on SCB-16: [~njiang] Could you please update or close this issue? > service communication with MQ > - > > Key: SCB-16 > URL: https://issues.apache.org/jira/browse/SCB-16 > Project: Apache ServiceComb > Issue Type: New Feature > Components: Saga >Reporter: Yin Xiang >Priority: Major > > as a user, i want to set up communication between saga and services with MQ, > so that they can handle transactions asynchronously -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-18) stateful service support
[ https://issues.apache.org/jira/browse/SCB-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yang Bo updated SCB-18: --- Fix Version/s: saga-0.3.0 > stateful service support > > > Key: SCB-18 > URL: https://issues.apache.org/jira/browse/SCB-18 > Project: Apache ServiceComb > Issue Type: New Feature > Components: Saga >Reporter: Yin Xiang >Priority: Major > Fix For: saga-0.3.0 > > > currently saga sub-transactions are load balanced to multiple service > instances with service discovery, but it doesn't work well with stateful > service. > stateful service support can either be supported with service registry or > caching request address in saga -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-21) service orchestration
[ https://issues.apache.org/jira/browse/SCB-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yang Bo updated SCB-21: --- Fix Version/s: java-chassis-1.0.0-m2 > service orchestration > - > > Key: SCB-21 > URL: https://issues.apache.org/jira/browse/SCB-21 > Project: Apache ServiceComb > Issue Type: New Feature > Components: Java-Chassis >Reporter: Eric Lee >Priority: Major > Fix For: java-chassis-1.0.0-m2 > > Attachments: Proposal for integrating ServiceComb into Camel.pdf > > > orchestration of service invocation and aggregation of data from multiple > services based on configured rule > eg. a user request requires calling service a/b/c/d in order: request -> a -> > b -> c -> d -> response > this creates a tight coupling among services a/b/c/d. > better solutions: > request -> aggregator -> response (aggregator calls a/b/c/d in sequence based > on configured rule) > request -> a -> message queue -> b -> queue -> c -> queue -> d > both ways no coupling among the services. > this epic is about solution 1 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-19) request json generator
[ https://issues.apache.org/jira/browse/SCB-19?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yang Bo updated SCB-19: --- Fix Version/s: saga-0.3.0 > request json generator > -- > > Key: SCB-19 > URL: https://issues.apache.org/jira/browse/SCB-19 > Project: Apache ServiceComb > Issue Type: New Feature > Components: Saga >Reporter: Yin Xiang >Priority: Major > Fix For: saga-0.3.0 > > > as a user, i want to generate saga request json by dragging and dropping > services on GUI, so that i can minimize the manual coding myself and avoid > human error -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-22) integration with service center
[ https://issues.apache.org/jira/browse/SCB-22?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yang Bo updated SCB-22: --- Fix Version/s: java-chassis-1.0.0-m1 > integration with service center > --- > > Key: SCB-22 > URL: https://issues.apache.org/jira/browse/SCB-22 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Java-Chassis >Reporter: Eric Lee >Priority: Major > Fix For: java-chassis-1.0.0-m1 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SCB-23) integration with zipkin
[ https://issues.apache.org/jira/browse/SCB-23?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16477107#comment-16477107 ] Yang Bo commented on SCB-23: [~njiang] This is done in 1.0.0-m1. Could you please close this issue? > integration with zipkin > --- > > Key: SCB-23 > URL: https://issues.apache.org/jira/browse/SCB-23 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Java-Chassis >Reporter: Eric Lee >Priority: Major > Fix For: java-chassis-1.0.0-m1 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SCB-22) integration with service center
[ https://issues.apache.org/jira/browse/SCB-22?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16477108#comment-16477108 ] Yang Bo commented on SCB-22: [~njiang] Could you please close this issue as it seems already fixed? > integration with service center > --- > > Key: SCB-22 > URL: https://issues.apache.org/jira/browse/SCB-22 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Java-Chassis >Reporter: Eric Lee >Priority: Major > Fix For: java-chassis-1.0.0-m1 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SCB-24) visualize transaction results
[ https://issues.apache.org/jira/browse/SCB-24?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16477105#comment-16477105 ] Yang Bo commented on SCB-24: Duplicated issue, could you please close this issue? > visualize transaction results > - > > Key: SCB-24 > URL: https://issues.apache.org/jira/browse/SCB-24 > Project: Apache ServiceComb > Issue Type: New Feature > Components: Saga >Reporter: Yin Xiang >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-23) integration with zipkin
[ https://issues.apache.org/jira/browse/SCB-23?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yang Bo updated SCB-23: --- Fix Version/s: java-chassis-1.0.0-m1 > integration with zipkin > --- > > Key: SCB-23 > URL: https://issues.apache.org/jira/browse/SCB-23 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Java-Chassis >Reporter: Eric Lee >Priority: Major > Fix For: java-chassis-1.0.0-m1 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-25) integration with highway transport
[ https://issues.apache.org/jira/browse/SCB-25?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yang Bo updated SCB-25: --- Fix Version/s: java-chassis-1.0.0-m2 > integration with highway transport > -- > > Key: SCB-25 > URL: https://issues.apache.org/jira/browse/SCB-25 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Java-Chassis >Reporter: Eric Lee >Priority: Major > Fix For: java-chassis-1.0.0-m2 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-27) parallel service invocations
[ https://issues.apache.org/jira/browse/SCB-27?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yang Bo updated SCB-27: --- Fix Version/s: java-chassis-1.0.0-m2 > parallel service invocations > > > Key: SCB-27 > URL: https://issues.apache.org/jira/browse/SCB-27 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Java-Chassis >Reporter: Eric Lee >Priority: Major > Fix For: java-chassis-1.0.0-m2 > > > *Given* > aggregator configured with parallel service invocations in a configuration > file > *When* > a request goes through services in parallel a/b/c/d without transformation of > data > *Then* > aggregator invokes the services a/b/c/d in parallel and returns the > aggregated responses from services a/b/c/d -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-26) serial service invocations
[ https://issues.apache.org/jira/browse/SCB-26?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yang Bo updated SCB-26: --- Fix Version/s: java-chassis-1.0.0-m2 > serial service invocations > -- > > Key: SCB-26 > URL: https://issues.apache.org/jira/browse/SCB-26 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Java-Chassis >Reporter: Eric Lee >Priority: Major > Fix For: java-chassis-1.0.0-m2 > > > *Given* > aggregator configured with serial service invocations in a configuration file > *When* > a request goes through services in order a -> b -> c -> d without > transformation of data > *Then* > aggregator invokes the services a/b/c/d in order and returns the response > from service d -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-28) fallback invocation on exception
[ https://issues.apache.org/jira/browse/SCB-28?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yang Bo updated SCB-28: --- Fix Version/s: java-chassis-1.0.0-m2 > fallback invocation on exception > > > Key: SCB-28 > URL: https://issues.apache.org/jira/browse/SCB-28 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Java-Chassis >Reporter: Eric Lee >Priority: Major > Fix For: java-chassis-1.0.0-m2 > > > *Given* > aggregator configured with service invocations with fallback in a > configuration file > *When* > a request goes through service a with fallback f without transformation of > data > *Then* > aggregator invokes the services a and returns its response on success > *When* > invocation of service a failed > *Then* > aggregator invokes service f and returns its response -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-29) Dynamic Configuration
[ https://issues.apache.org/jira/browse/SCB-29?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yang Bo updated SCB-29: --- Fix Version/s: java-chassis-1.0.0-m2 > Dynamic Configuration > - > > Key: SCB-29 > URL: https://issues.apache.org/jira/browse/SCB-29 > Project: Apache ServiceComb > Issue Type: New Feature > Components: Java-Chassis >Reporter: mabin >Priority: Major > Fix For: java-chassis-1.0.0-m2 > > > as a user, i want to update my microservice configurations from a centralized > server, so that i don't have restart and re-deploy each of my services. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SCB-50) Support to call the dubbo service
[ https://issues.apache.org/jira/browse/SCB-50?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16477096#comment-16477096 ] Yang Bo commented on SCB-50: [~njiang] Dubbo support is added and tracked by other issues, could you update or close this issue? > Support to call the dubbo service > - > > Key: SCB-50 > URL: https://issues.apache.org/jira/browse/SCB-50 > Project: Apache ServiceComb > Issue Type: New Feature > Components: Saga >Reporter: Yin Xiang >Priority: Major > Fix For: saga-0.2.0 > > > to support calling dubbo services -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SCB-69) Provide MicroService project scaffold as JHipster does
[ https://issues.apache.org/jira/browse/SCB-69?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16477092#comment-16477092 ] Yang Bo commented on SCB-69: Scaffolding is provided and tracked by other issues, could you please close this issue? > Provide MicroService project scaffold as JHipster does > -- > > Key: SCB-69 > URL: https://issues.apache.org/jira/browse/SCB-69 > Project: Apache ServiceComb > Issue Type: Wish > Components: Java-Chassis >Reporter: Bo Li >Priority: Major > Fix For: java-chassis-1.0.0-m2 > > > ServiceComb是否有一个类似于JHipster这样包含完整的脚手架功能的微服务构建工具， > 尤其是针对典型的应用场景，对企业应用开发用户来说透明，直接通过脚手架或者插件进行配置和构建，只要关注业务开发就好了。 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SCB-67) Swagger exception is throw when registering the service
[
https://issues.apache.org/jira/browse/SCB-67?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16477094#comment-16477094
]
Yang Bo commented on SCB-67:
Could you please add more information close this issue?
> Swagger exception is throw when registering the service
> ---
>
> Key: SCB-67
> URL: https://issues.apache.org/jira/browse/SCB-67
> Project: Apache ServiceComb
> Issue Type: Bug
> Components: Java-Chassis
>Reporter: Bo Li
>Priority: Major
>
> 定义的每个RestController都返回ResponseEntity，例如
> @requestmapping(value = "/", method = RequestMethod.POST)
> public ResponseEntity customerInfo(@requestbody CustomerInfo customerInfo,
> HttpServletRequest request)
> CustomerInfo.java
> public class CustomerInfo {
> // 项目ID
> @jsonproperty(value = "PrecinctID",required = true)
> private Long precinctID;
> // 客户姓名
> @jsonproperty(value = "CustomerName",required = true)
> private String customerName;
> // 手机号码1
> @jsonproperty(value = "MobilePhone1",required = true)
> private String mobilePhone1;
> // 经纪人编号
> @jsonproperty(value = "BrokerID",required = true)
> private Long brokerID;
> // 经纪人姓名
> @jsonproperty(value = "BrokerName",required = true)
> private String brokerName;
> // 内部经纪人ID
> @jsonproperty(value = "ConsultantID",required = true)
> private Long consultantID;
> // 外部系统来源
> @jsonproperty(value = "SourceType",required = true)
> private Integer sourceType;
> }
> post:
> operationId: "customerInfo"
> parameters:
> - in: "body"
> name: "customerInfo"
> required: false
> schema:
> $ref: "#/definitions/data"
> responses:
> 200:
> description: "response of 200"
> schema:
> type: "string"
> 其它几个接口的参数中也都没有引用到Object类型
> 异常信息如下
> ArrayIndexOutOfBoundsException.txt
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (SCB-50) Support to call the dubbo service
[ https://issues.apache.org/jira/browse/SCB-50?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yang Bo updated SCB-50: --- Fix Version/s: saga-0.2.0 > Support to call the dubbo service > - > > Key: SCB-50 > URL: https://issues.apache.org/jira/browse/SCB-50 > Project: Apache ServiceComb > Issue Type: New Feature > Components: Saga >Reporter: Yin Xiang >Priority: Major > Fix For: saga-0.2.0 > > > to support calling dubbo services -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-69) Provide MicroService project scaffold as JHipster does
[ https://issues.apache.org/jira/browse/SCB-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yang Bo updated SCB-69: --- Fix Version/s: java-chassis-1.0.0-m2 > Provide MicroService project scaffold as JHipster does > -- > > Key: SCB-69 > URL: https://issues.apache.org/jira/browse/SCB-69 > Project: Apache ServiceComb > Issue Type: Wish > Components: Java-Chassis >Reporter: Bo Li >Priority: Major > Fix For: java-chassis-1.0.0-m2 > > > ServiceComb是否有一个类似于JHipster这样包含完整的脚手架功能的微服务构建工具， > 尤其是针对典型的应用场景，对企业应用开发用户来说透明，直接通过脚手架或者插件进行配置和构建，只要关注业务开发就好了。 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SCB-70) Question about loadblance
[ https://issues.apache.org/jira/browse/SCB-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16477087#comment-16477087 ] Yang Bo commented on SCB-70: Could you please add more information close this issue? > Question about loadblance > - > > Key: SCB-70 > URL: https://issues.apache.org/jira/browse/SCB-70 > Project: Apache ServiceComb > Issue Type: Bug > Components: Java-Chassis >Reporter: Bo Li >Priority: Major > > 我想使用负载均衡功能，按照官网的说明配置了pojo-consumer的microservice.yaml。以下是我实验的大致过程： > 我启动多个pojo-provider实例在不同的端口，然后启动pojo-consumer，一切都正常。可是当我关掉一个pojo-provider实例时，pojo-consumer调用服务接口就失败了。 > 按我的理解，pojo-consumer在当前调用实例断开后，应该自动切换到另外一个pojo-provider实例上调用服务接口继续工作，然而实验结果并不是这样的。 > 请问我对ServiceComb负载均衡的理解是否有出错？ > 另外，能否增加microservice.yaml各配置项的使用说明。 > 非常感谢 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-72) Can isolation information of provider and consumer been discovered through capability of release and subscription?
[ https://issues.apache.org/jira/browse/SCB-72?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yang Bo updated SCB-72: --- Fix Version/s: java-chassis-1.0.0-m2 > Can isolation information of provider and consumer been discovered through > capability of release and subscription? > -- > > Key: SCB-72 > URL: https://issues.apache.org/jira/browse/SCB-72 > Project: Apache ServiceComb > Issue Type: Bug > Components: Java-Chassis >Reporter: Bo Li >Priority: Major > Fix For: java-chassis-1.0.0-m2 > > > There could be internal wrong when current service is isolated, although > loadbalance can be used to filter abnormal service, extra method to get that > kind for information is still in need, Please fix. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-74) POJO static method is export as an operation
[
https://issues.apache.org/jira/browse/SCB-74?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yang Bo updated SCB-74:
---
Fix Version/s: java-chassis-1.0.0-m2
> POJO static method is export as an operation
>
>
> Key: SCB-74
> URL: https://issues.apache.org/jira/browse/SCB-74
> Project: Apache ServiceComb
> Issue Type: Bug
> Components: Java-Chassis
>Reporter: Bo Li
>Priority: Major
> Fix For: java-chassis-1.0.0-m2
>
>
> When using @rpcschema to expose a singleton POJO as schema interface, then
> call the public method of the class which the method belong to, exception
> occurs as follow:
> {code}
> Exception in thread "main" java.lang.NullPointerException
> at
> io.servicecomb.swagger.generator.core.utils.ClassUtils.getOrCreateClass(ClassUtils.java:135)
> at
> io.servicecomb.swagger.converter.model.ModelImplConverter.doConvert(ModelImplConverter.java:55)
> at
> io.servicecomb.swagger.converter.AbstractConverter.convert(AbstractConverter.java:42)
> at
> io.servicecomb.swagger.converter.ConverterMgr.findJavaType(ConverterMgr.java:188)
> at
> io.servicecomb.swagger.converter.ConverterMgr.findByRef(ConverterMgr.java:196)
> at
> io.servicecomb.swagger.converter.property.RefPropertyConverter.doConvert(RefPropertyConverter.java:30)
> at
> io.servicecomb.swagger.converter.AbstractConverter.convert(AbstractConverter.java:42)
> at
> io.servicecomb.swagger.converter.ConverterMgr.findJavaType(ConverterMgr.java:188)
> at
> io.servicecomb.swagger.generator.core.utils.ClassUtils.createInterface(ClassUtils.java:252)
> at
> io.servicecomb.swagger.generator.core.utils.ClassUtils.getOrCreateInterface(ClassUtils.java:237)
> at io.servicecomb.core.definition.SchemaMeta.(SchemaMeta.java:65)
> at
> io.servicecomb.core.definition.loader.SchemaLoader.registerSchema(SchemaLoader.java:92)
> at
> io.servicecomb.core.definition.schema.ConsumerSchemaFactory.createSchema(ConsumerSchemaFactory.java:132)
> at
> io.servicecomb.core.definition.schema.ConsumerSchemaFactory.createSchema(ConsumerSchemaFactory.java:33)
> at
> io.servicecomb.core.definition.schema.AbstractSchemaFactory.getOrCreateSchema(AbstractSchemaFactory.java:59)
> at
> io.servicecomb.core.definition.schema.ConsumerSchemaFactory.getOrCreateConsumerSchema(ConsumerSchemaFactory.java:122)
> at
> io.servicecomb.core.definition.schema.ConsumerSchemaFactory.getOrCreateMicroserviceMeta(ConsumerSchemaFactory.java:78)
> at
> io.servicecomb.core.provider.consumer.ReferenceConfig.(ReferenceConfig.java:35)
> at
> io.servicecomb.core.provider.consumer.ConsumerProviderManager.getReferenceConfig(ConsumerProviderManager.java:82)
> at
> io.servicecomb.core.provider.consumer.ReferenceConfigUtils.getForInvoke(ReferenceConfigUtils.java:42)
> at io.servicecomb.provider.pojo.Invoker.prepare(Invoker.java:59)
> at io.servicecomb.provider.pojo.Invoker.invoke(Invoker.java:81)
> at com.sun.proxy.$Proxy17.selectByPrimaryKey(Unknown Source)
> at com.ceewa.cloud.consumer.DubboxConsumer.testMycat(DubboxConsumer.java:49)
> at com.ceewa.cloud.consumer.DubboxConsumer.main(DubboxConsumer.java:38)
> {code}
> Problem is fixed after adding {code}@apioperation(value = "getInstance is not
> an endpoint", hidden = true){code} tag for method getInstance, is there any
> good suggestions for that question?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (SCB-72) Can isolation information of provider and consumer been discovered through capability of release and subscription?
[ https://issues.apache.org/jira/browse/SCB-72?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yang Bo updated SCB-72: --- Component/s: Java-Chassis > Can isolation information of provider and consumer been discovered through > capability of release and subscription? > -- > > Key: SCB-72 > URL: https://issues.apache.org/jira/browse/SCB-72 > Project: Apache ServiceComb > Issue Type: Bug > Components: Java-Chassis >Reporter: Bo Li >Priority: Major > Fix For: java-chassis-1.0.0-m2 > > > There could be internal wrong when current service is isolated, although > loadbalance can be used to filter abnormal service, extra method to get that > kind for information is still in need, Please fix. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SCB-76) error log has insufficient information when type not supported
[ https://issues.apache.org/jira/browse/SCB-76?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16477084#comment-16477084 ] Yang Bo commented on SCB-76: Could you please add more information close this issue? > error log has insufficient information when type not supported > --- > > Key: SCB-76 > URL: https://issues.apache.org/jira/browse/SCB-76 > Project: Apache ServiceComb > Issue Type: Bug > Components: Java-Chassis >Reporter: Bo Li >Priority: Major > Labels: newbie > > this error is thrown when a certain is not supported in controller > java.lang.Error: not support def type: class > io.swagger.models.properties.BaseIntegerProperty > the type BaseIntegerProperty is not what user specified and the user > specified type is not shown in log -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SCB-75) Why it must be json format when receiving bytes through @RequestBody byte[] buffer
[
https://issues.apache.org/jira/browse/SCB-75?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16477085#comment-16477085
]
Yang Bo commented on SCB-75:
Could you please add more information close this issue?
> Why it must be json format when receiving bytes through @RequestBody byte[]
> buffer
> --
>
> Key: SCB-75
> URL: https://issues.apache.org/jira/browse/SCB-75
> Project: Apache ServiceComb
> Issue Type: Bug
>Reporter: Bo Li
>Priority: Major
>
> Parameter invalid error occurs when received data is not json format when
> using @requestbody byte[] buffer
> {code}
> @RequestMapping(value = "/update", method = RequestMethod.PUT)
> public ResponseEntity update(@PathVariable("accountId") Long
> accountId,
> @RequestHeader("Date") String date,
> @RequestBody byte[] buffer, HttpServletRequest request)
> {
>byte[] data = buffer; //buffer data have to be json format here
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (SCB-78) Request body is always null when using request.getinputstream
[
https://issues.apache.org/jira/browse/SCB-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16477083#comment-16477083
]
Yang Bo commented on SCB-78:
Could you please add more information close this issue?
> Request body is always null when using request.getinputstream
> -
>
> Key: SCB-78
> URL: https://issues.apache.org/jira/browse/SCB-78
> Project: Apache ServiceComb
> Issue Type: Bug
> Components: Java-Chassis
>Reporter: Bo Li
>Priority: Major
>
> {code}
>@RequestMapping(value = "/", method = {RequestMethod.GET})
> public String something(@PathVariable(value = "appId") String appId,
> Model model,
> HttpServletRequest httpRequest) {
> httpRequest.getInputStream();// always ""
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (SCB-79) Value of Content-Length is null when using @ReaustHeader("Content-Length")
[
https://issues.apache.org/jira/browse/SCB-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16477081#comment-16477081
]
Yang Bo commented on SCB-79:
Could you please add more information close this issue?
> Value of Content-Length is null when using @ReaustHeader("Content-Length")
> ---
>
> Key: SCB-79
> URL: https://issues.apache.org/jira/browse/SCB-79
> Project: Apache ServiceComb
> Issue Type: Bug
> Components: Java-Chassis
>Reporter: Bo Li
>Priority: Major
>
> Using @RequesHeader to get value of Content-Length doesn't work.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (SCB-80) ResponseEntity Type error occurs
[
https://issues.apache.org/jira/browse/SCB-80?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16477068#comment-16477068
]
Yang Bo commented on SCB-80:
Could you please add more information close this issue?
> ResponseEntity Type error occurs
> -
>
> Key: SCB-80
> URL: https://issues.apache.org/jira/browse/SCB-80
> Project: Apache ServiceComb
> Issue Type: Bug
> Components: Java-Chassis
>Reporter: Bo Li
>Priority: Major
>
> Given:
> * tomcat 8.5.x
> * java-chassis 0.4.0
> * service-center 1.0.1
> if header and body included in responseEntity, error 1 and error 2 occurs, if
> not, only error 2 occurs.
> error 1:
> {code}
> [2017-11-22
> 16:36:39.101][ufm][][ERROR][io.servicecomb.common.rest.AbstractRestInvocation][sendResponseQuietly,131][Failed
> to send rest response,
> operation:ufm.api-v2-accounts.setWatermark.][pool-30-thread-3]
> java.lang.NullPointerException: null
> at
> org.apache.coyote.http11.Http11OutputBuffer.commit(Http11OutputBuffer.java:368)
> at
> org.apache.coyote.http11.Http11Processor.prepareResponse(Http11Processor.java:1300)
> at
> org.apache.coyote.AbstractProcessor.action(AbstractProcessor.java:254)
> at org.apache.coyote.Response.action(Response.java:174)
> at org.apache.coyote.Response.sendHeaders(Response.java:356)
> at
> org.apache.catalina.connector.OutputBuffer.doFlush(OutputBuffer.java:303)
> at
> org.apache.catalina.connector.OutputBuffer.flush(OutputBuffer.java:284)
> at org.apache.catalina.connector.Response.flushBuffer(Response.java:541)
> at
> org.apache.catalina.connector.ResponseFacade.flushBuffer(ResponseFacade.java:312)
> at
> javax.servlet.ServletResponseWrapper.flushBuffer(ServletResponseWrapper.java:176)
> at
> io.servicecomb.foundation.vertx.http.StandardHttpServletResponseEx.flushBuffer(StandardHttpServletResponseEx.java:80)
> at
> io.servicecomb.common.rest.AbstractRestInvocation.sendResponse(AbstractRestInvocation.java:164)
> at
> io.servicecomb.common.rest.AbstractRestInvocation.sendResponseQuietly(AbstractRestInvocation.java:129)
> at
> io.servicecomb.common.rest.RestProducerInvocation.lambda$doInvoke$1(RestProducerInvocation.java:121)
> at
> io.servicecomb.core.handler.ShutdownHookHandler.lambda$handle$0(ShutdownHookHandler.java:70)
> at
> io.servicecomb.swagger.engine.SwaggerProducerOperation.invoke(SwaggerProducerOperation.java:113)
> at
> io.servicecomb.core.handler.impl.ProducerOperationHandler.handle(ProducerOperationHandler.java:38)
> at io.servicecomb.core.Invocation.next(Invocation.java:132)
> at
> io.servicecomb.core.handler.ShutdownHookHandler.handle(ShutdownHookHandler.java:68)
> at io.servicecomb.core.Invocation.next(Invocation.java:132)
> at
> io.servicecomb.common.rest.RestProducerInvocation.doInvoke(RestProducerInvocation.java:120)
> at
> io.servicecomb.common.rest.AbstractRestInvocation.invoke(AbstractRestInvocation.java:93)
> at
> io.servicecomb.common.rest.RestProducerInvocation.runOnExecutor(RestProducerInvocation.java:94)
> at
> io.servicecomb.common.rest.RestProducerInvocation.lambda$scheduleInvocation$0(RestProducerInvocation.java:80)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> error 2
> {code}
> [2017-11-22
> 16:36:39.105][ufm][][ERROR][io.servicecomb.common.rest.AbstractRestInvocation][invoke,95][unknown
> edge exception.][pool-30-thread-3]
> java.lang.IllegalStateException: It is illegal to call this method if the
> current request is not in asynchronous mode (i.e. isAsyncStarted() returns
> false)
> at
> org.apache.catalina.connector.Request.getAsyncContext(Request.java:1742)
> at
> org.apache.catalina.connector.RequestFacade.getAsyncContext(RequestFacade.java:1056)
> at
> javax.servlet.ServletRequestWrapper.getAsyncContext(ServletRequestWrapper.java:431)
> at
> io.servicecomb.common.rest.AbstractRestInvocation.sendResponseQuietly(AbstractRestInvocation.java:135)
> at
> io.servicecomb.common.rest.RestProducerInvocation.lambda$doInvoke$1(RestProducerInvocation.java:121)
> at
> io.servicecomb.core.handler.ShutdownHookHandler.lambda$handle$0(ShutdownHookHandler.java:70)
> at
> io.servicecomb.swagger.engine.SwaggerProducerOperation.invoke(SwaggerProducerOperation.java:113)
> at
> io.servicecomb.core.handler.impl.ProducerOperationHandler.handle(ProducerOperationHandler.java:38)
> at io.servicecomb.core.Invocation.next(Invocation.java:132)
> at
>
[jira] [Commented] (SCB-81) Question about yaml file version
[ https://issues.apache.org/jira/browse/SCB-81?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16477067#comment-16477067 ] Yang Bo commented on SCB-81: Could you please close this issue? > Question about yaml file version > > > Key: SCB-81 > URL: https://issues.apache.org/jira/browse/SCB-81 > Project: Apache ServiceComb > Issue Type: Bug > Components: Java-Chassis >Reporter: Bo Li >Priority: Major > > * how to user yaml file version, i notived that microservice.yaml file's > version is 0.0.3. > * what's the relation between the three number separated by dot above? > * is there any limit of those numbers? what's tha maximum? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SCB-83) BMI Calculator throws exception
[
https://issues.apache.org/jira/browse/SCB-83?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16477064#comment-16477064
]
Yang Bo commented on SCB-83:
Could you please add more information or close this issue?
> BMI Calculator throws exception
> ---
>
> Key: SCB-83
> URL: https://issues.apache.org/jira/browse/SCB-83
> Project: Apache ServiceComb
> Issue Type: Bug
> Components: Java-Chassis
>Reporter: Bo Li
>Priority: Major
>
> when running BMI Calculator repeatly, it throws:
> {code}
> Internal Server Error: com.netflix.zuul.exception.ZuulException
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (SCB-82) NoClassDefFoundError occurs when creating Provider service following "QuickStart"
[
https://issues.apache.org/jira/browse/SCB-82?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16477065#comment-16477065
]
Yang Bo commented on SCB-82:
Could you please add more information or close this issue?
> NoClassDefFoundError occurs when creating Provider service following
> "QuickStart"
> -
>
> Key: SCB-82
> URL: https://issues.apache.org/jira/browse/SCB-82
> Project: Apache ServiceComb
> Issue Type: Bug
> Components: Java-Chassis
>Reporter: Bo Li
>Priority: Major
>
> {code}
> java.lang.NoClassDefFoundError: com/fasterxml/jackson/core/FormatFeature
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (SCB-84) Is there a interface for user to find service according to schemaId
[ https://issues.apache.org/jira/browse/SCB-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16477062#comment-16477062 ] Yang Bo commented on SCB-84: Could you please close this issue? > Is there a interface for user to find service according to schemaId > --- > > Key: SCB-84 > URL: https://issues.apache.org/jira/browse/SCB-84 > Project: Apache ServiceComb > Issue Type: Bug > Components: Java-Chassis >Reporter: Bo Li >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SCB-87) can anyone provide a gradle script?
[ https://issues.apache.org/jira/browse/SCB-87?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16477061#comment-16477061 ] Yang Bo commented on SCB-87: Could you please close this issue? Gradle support is tracked by another issue. > can anyone provide a gradle script? > --- > > Key: SCB-87 > URL: https://issues.apache.org/jira/browse/SCB-87 > Project: Apache ServiceComb > Issue Type: Bug > Components: Java-Chassis >Reporter: Bo Li >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SCB-93) inconsistent configuration folders
[ https://issues.apache.org/jira/browse/SCB-93?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16477058#comment-16477058 ] Yang Bo commented on SCB-93: Could you please close this issue > inconsistent configuration folders > -- > > Key: SCB-93 > URL: https://issues.apache.org/jira/browse/SCB-93 > Project: Apache ServiceComb > Issue Type: Bug > Components: Service-Center >Reporter: Bo Li >Priority: Major > > he certificates stores under etc/ssl folder, while the application > configuration files stores under conf folder, which looks inconsistent. Is it > a better idea to merge both of it under etc folder? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SCB-94) How about changing the log module to logus or other opensource project?
[ https://issues.apache.org/jira/browse/SCB-94?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16477054#comment-16477054 ] Yang Bo commented on SCB-94: Could you please close this issue? > How about changing the log module to logus or other opensource project? > --- > > Key: SCB-94 > URL: https://issues.apache.org/jira/browse/SCB-94 > Project: Apache ServiceComb > Issue Type: Bug > Components: Service-Center >Reporter: Bo Li >Priority: Major > > How about to change the log module to logus or other opensource project? > https://github.com/ServiceComb/service-center/tree/master/lager -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-102) As a developer, I want to work in reactive mode to improve performance
[ https://issues.apache.org/jira/browse/SCB-102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yang Bo updated SCB-102: Fix Version/s: java-chassis-1.0.0-m2 > As a developer, I want to work in reactive mode to improve performance > -- > > Key: SCB-102 > URL: https://issues.apache.org/jira/browse/SCB-102 > Project: Apache ServiceComb > Issue Type: New Feature > Components: Java-Chassis >Reporter: wujimin >Assignee: wujimin >Priority: Major > Labels: features, performance > Fix For: java-chassis-1.0.0-m2 > > > As a developer, I want to work in reactive mode to improve performance -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SCB-113) Metrics document translation
[ https://issues.apache.org/jira/browse/SCB-113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16477052#comment-16477052 ] Yang Bo commented on SCB-113: - Could you please update the status of this issue? > Metrics document translation > > > Key: SCB-113 > URL: https://issues.apache.org/jira/browse/SCB-113 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: website >Reporter: Bo Li >Priority: Major > > Just Metrics document need to translate. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SCB-111) General Development Translation
[ https://issues.apache.org/jira/browse/SCB-111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16477053#comment-16477053 ] Yang Bo commented on SCB-111: - Could you please resolve this issue? > General Development Translation > --- > > Key: SCB-111 > URL: https://issues.apache.org/jira/browse/SCB-111 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: website >Reporter: Bo Li >Priority: Major > > General Development Translation contains following part: > # Develop and Test in Local Environment > # User ServiceComb in SpringBoot > # Distribute Tracing > # Customized Tracing -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SCB-119) Added community and release section
[ https://issues.apache.org/jira/browse/SCB-119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16477051#comment-16477051 ] Yang Bo commented on SCB-119: - Seems this is finished. Could you please update and resolve? > Added community and release section > > > Key: SCB-119 > URL: https://issues.apache.org/jira/browse/SCB-119 > Project: Apache ServiceComb > Issue Type: Task > Components: website >Reporter: Willem Jiang >Priority: Major > Labels: easyfix, newbie > > We need to update the community and release section in the website. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SCB-121) Section header missed for servicecomb website document at run-mode part.
[ https://issues.apache.org/jira/browse/SCB-121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16477048#comment-16477048 ] Yang Bo commented on SCB-121: - [~Bo Li] Could you please update and resolve this issue. > Section header missed for servicecomb website document at run-mode part. > > > Key: SCB-121 > URL: https://issues.apache.org/jira/browse/SCB-121 > Project: Apache ServiceComb > Issue Type: Bug > Components: website >Reporter: Bo Li >Priority: Minor > > Only step 2 for run-mode at http://servicecomb.io/users/run-mode/ at WEB > container mode section shows up. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-139) Optimization suggestions for README
[ https://issues.apache.org/jira/browse/SCB-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yang Bo updated SCB-139: Fix Version/s: java-chassis-1.0.0-m2 > Optimization suggestions for README > --- > > Key: SCB-139 > URL: https://issues.apache.org/jira/browse/SCB-139 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Java-Chassis >Reporter: mabin >Priority: Major > Fix For: java-chassis-1.0.0-m2 > > > For the user to understand chassis quickly, it is better to added some more > summary informations in README, eg. > 1.Major features list > 2.Summary design graph > 3.Module dependency graph > 4.Complete quick start guide > 5.FAQ > What is your opinion? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-163) [pack] async transaction support with bytecode instrumentation
[ https://issues.apache.org/jira/browse/SCB-163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yang Bo updated SCB-163: Fix Version/s: saga-0.3.0 > [pack] async transaction support with bytecode instrumentation > -- > > Key: SCB-163 > URL: https://issues.apache.org/jira/browse/SCB-163 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Saga >Reporter: Yin Xiang >Priority: Major > Fix For: saga-0.3.0 > > > to support more async framework, bytecode instrumentation is probably better > to avoid invasive code changes on user side -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-170) [pack] separate serialization from grpc to reuse the same stream
[ https://issues.apache.org/jira/browse/SCB-170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yang Bo updated SCB-170: Fix Version/s: saga-0.3.0 > [pack] separate serialization from grpc to reuse the same stream > > > Key: SCB-170 > URL: https://issues.apache.org/jira/browse/SCB-170 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Saga >Reporter: Yin Xiang >Priority: Major > Fix For: saga-0.3.0 > > > currently, messaging protocol, serialization, and transportation are all done > with grpc/protobuf. > doing so makes sharing a single stream among different messages hard to do. > a better way is to separate serialization from grpc. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-178) Provide access log of highway
[ https://issues.apache.org/jira/browse/SCB-178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yang Bo updated SCB-178: Fix Version/s: java-chassis-1.0.0-m2 > Provide access log of highway > - > > Key: SCB-178 > URL: https://issues.apache.org/jira/browse/SCB-178 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Java-Chassis >Reporter: YaoHaishi >Assignee: YaoHaishi >Priority: Minor > Fix For: java-chassis-1.0.0-m2 > > > Provide highway access log similar to Tomcat access log -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-175) Provide accesslog for the microservice
[ https://issues.apache.org/jira/browse/SCB-175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yang Bo updated SCB-175: Fix Version/s: java-chassis-1.0.0-m2 > Provide accesslog for the microservice > --- > > Key: SCB-175 > URL: https://issues.apache.org/jira/browse/SCB-175 > Project: Apache ServiceComb > Issue Type: New Feature > Components: Java-Chassis >Reporter: YaoHaishi >Assignee: YaoHaishi >Priority: Minor > Fix For: java-chassis-1.0.0-m2 > > > As a SDK user, I need to record accesslog so that I can record all of my > access in each microservice for the debugging purpose > moved from [https://servicecomb.atlassian.net/browse/JAV-561] > 1.provide a mechanism to generate traceId > 2.create a new project, inherit from http header or init tranceId in > invocation context, event not use trace like zipkin/pinpoint/apm and so on. > 3.accessLog for consumer and producer ,both include traceId -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-194) Improve component-scan setting
[ https://issues.apache.org/jira/browse/SCB-194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yang Bo updated SCB-194: Fix Version/s: java-chassis-1.0.0-m2 > Improve component-scan setting > -- > > Key: SCB-194 > URL: https://issues.apache.org/jira/browse/SCB-194 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Java-Chassis >Reporter: yangyongzheng >Priority: Major > Fix For: java-chassis-1.0.0-m2 > > > Current in Producer side,we need add META-INF/spring/xxx.bean.xml file > contains: > > in order to define base package path,we may need find a way to add main class > package to component-scan path automatically -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-191) consumer get response header when return CompletableFuture
[ https://issues.apache.org/jira/browse/SCB-191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yang Bo updated SCB-191: Fix Version/s: java-chassis-1.0.0-m2 > consumer get response header when return CompletableFuture > -- > > Key: SCB-191 > URL: https://issues.apache.org/jira/browse/SCB-191 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Java-Chassis >Reporter: wujimin >Assignee: wujimin >Priority: Major > Fix For: java-chassis-1.0.0-m2 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-206) Support @Api to specify produces and consumes
[ https://issues.apache.org/jira/browse/SCB-206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yang Bo updated SCB-206: Component/s: Java-Chassis > Support @Api to specify produces and consumes > - > > Key: SCB-206 > URL: https://issues.apache.org/jira/browse/SCB-206 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Java-Chassis >Reporter: YaoHaishi >Assignee: YaoHaishi >Priority: Trivial > Fix For: java-chassis-1.0.0-m2 > > > At present, ServiceComb only process the `tags` of > io.swagger.annotations.Api. If user specify produces and consumes in `@Api`, > nothing will happen. > The support to these two fields should be added if necessary. The hierarchy > relationship of `SwaggerDefinition`, `Api`, `ApiOperation` is that `Api` > overrides `SwaggerDefinition`, `ApiOperation` overrides `Api`. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-206) Support @Api to specify produces and consumes
[ https://issues.apache.org/jira/browse/SCB-206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yang Bo updated SCB-206: Fix Version/s: java-chassis-1.0.0-m2 > Support @Api to specify produces and consumes > - > > Key: SCB-206 > URL: https://issues.apache.org/jira/browse/SCB-206 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Java-Chassis >Reporter: YaoHaishi >Assignee: YaoHaishi >Priority: Trivial > Fix For: java-chassis-1.0.0-m2 > > > At present, ServiceComb only process the `tags` of > io.swagger.annotations.Api. If user specify produces and consumes in `@Api`, > nothing will happen. > The support to these two fields should be added if necessary. The hierarchy > relationship of `SwaggerDefinition`, `Api`, `ApiOperation` is that `Api` > overrides `SwaggerDefinition`, `ApiOperation` overrides `Api`. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-207) Fix known defects related to SCB-184
[
https://issues.apache.org/jira/browse/SCB-207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yang Bo updated SCB-207:
Fix Version/s: java-chassis-1.0.0-m2
> Fix known defects related to SCB-184
>
>
> Key: SCB-207
> URL: https://issues.apache.org/jira/browse/SCB-207
> Project: Apache ServiceComb
> Issue Type: Improvement
> Components: Java-Chassis
>Reporter: liubao
>Assignee: liubao
>Priority: Major
> Fix For: java-chassis-1.0.0-m2
>
>
> 1. As commented by users, when using ribbon, need to configure
> @Bean
> ServerList ribbonServerList(
> IClientConfig config) {
> ServiceCombServerList serverList = new ServiceCombServerList();
> serverList.initWithNiwsConfig(config);
> return serverList;
> }
> we need to provide a convenient way to hide all default ribbon
> configurations just like spring-cloud-starters-eureka
> 2. CseDiscoveryClient & ServiceCombList construct target type can be cached
> by DiscoveryTree, implements a filter can improve performance.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (SCB-215) support annotation ApiParam, so that user can change collection-format
[ https://issues.apache.org/jira/browse/SCB-215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yang Bo updated SCB-215: Fix Version/s: java-chassis-1.0.0-m2 > support annotation ApiParam, so that user can change collection-format > -- > > Key: SCB-215 > URL: https://issues.apache.org/jira/browse/SCB-215 > Project: Apache ServiceComb > Issue Type: New Feature > Components: Java-Chassis >Reporter: TaoMeng >Assignee: wujimin >Priority: Major > Fix For: java-chassis-1.0.0-m2 > > > https://github.com/apache/incubator-servicecomb-java-chassis/pull/497 > we have multiple leve information: > 1.class annotation > 2.method annotation > 3.normal parameter annotation > 4.special parameter annotation > 5.default setting > build a mechanism to calculate result. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-229) support rxJava Observable
[ https://issues.apache.org/jira/browse/SCB-229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yang Bo updated SCB-229: Fix Version/s: java-chassis-1.0.0-m2 > support rxJava Observable > - > > Key: SCB-229 > URL: https://issues.apache.org/jira/browse/SCB-229 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Java-Chassis >Affects Versions: java-chassis-1.0.0-m2 >Reporter: wujimin >Assignee: Bo Li >Priority: Major > Fix For: java-chassis-1.0.0-m2 > > > just like CompletableFuture -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-241) [pack] visualize transaction status in alpha
[ https://issues.apache.org/jira/browse/SCB-241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yang Bo updated SCB-241: Fix Version/s: saga-0.3.0 > [pack] visualize transaction status in alpha > > > Key: SCB-241 > URL: https://issues.apache.org/jira/browse/SCB-241 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Saga >Affects Versions: saga-0.2.0 >Reporter: Eric Lee >Priority: Major > Fix For: saga-0.3.0 > > > as a user, I want to see real time transaction status and query history > transaction status to better analysis the whole system. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-257) As a developer, I want to download file from microservice
[ https://issues.apache.org/jira/browse/SCB-257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yang Bo updated SCB-257: Fix Version/s: java-chassis-1.0.0-m2 > As a developer, I want to download file from microservice > - > > Key: SCB-257 > URL: https://issues.apache.org/jira/browse/SCB-257 > Project: Apache ServiceComb > Issue Type: New Feature > Components: Java-Chassis >Reporter: wujimin >Assignee: wujimin >Priority: Major > Fix For: java-chassis-1.0.0-m2 > > > not only download > but also need to support after download delete temp file. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-267) support generic for highway
[ https://issues.apache.org/jira/browse/SCB-267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yang Bo updated SCB-267: Fix Version/s: (was: java-chassis-1.0.0-m2) Java-chassis-1.0.0 > support generic for highway > --- > > Key: SCB-267 > URL: https://issues.apache.org/jira/browse/SCB-267 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Java-Chassis >Reporter: wujimin >Assignee: wujimin >Priority: Major > Fix For: Java-chassis-1.0.0 > > > protoStuff do not support generic > it's hard to do this.. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-268) [pack] compact events to remove unnecessary fields
[ https://issues.apache.org/jira/browse/SCB-268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yang Bo updated SCB-268: Fix Version/s: saga-0.3.0 > [pack] compact events to remove unnecessary fields > -- > > Key: SCB-268 > URL: https://issues.apache.org/jira/browse/SCB-268 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Saga >Reporter: Yin Xiang >Assignee: Willem Jiang >Priority: Major > Fix For: saga-0.3.0 > > > only TxStartedEvent needs to contain all tx information. > Asking other events to provide info such as payloads, compensationMethod, > parentTxId, etc. is not necessary. > > compacting events not only reduces network load and null/duplicate data in > database -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-273) proper indent for navigation
[ https://issues.apache.org/jira/browse/SCB-273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yang Bo updated SCB-273: Component/s: website > proper indent for navigation > > > Key: SCB-273 > URL: https://issues.apache.org/jira/browse/SCB-273 > Project: Apache ServiceComb > Issue Type: Bug > Components: website >Reporter: Eric Lee >Assignee: Eric Lee >Priority: Major > > Currently, the indent in _data/navigation.yml is incorrect in the yaml > format. Local server refuse to start because of it. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-258) [pack] idempotent support
[ https://issues.apache.org/jira/browse/SCB-258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yang Bo updated SCB-258: Fix Version/s: saga-0.3.0 > [pack] idempotent support > - > > Key: SCB-258 > URL: https://issues.apache.org/jira/browse/SCB-258 > Project: Apache ServiceComb > Issue Type: New Feature > Components: Saga >Reporter: Yin Xiang >Priority: Major > Fix For: saga-0.3.0 > > > implementing idempotent at service level is hard. > with pack, it is possible to support idempotent with omega backed by alpha. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-265) Support generic type in input parameter or response type
[ https://issues.apache.org/jira/browse/SCB-265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yang Bo updated SCB-265: Fix Version/s: java-chassis-1.0.0-m2 > Support generic type in input parameter or response type > > > Key: SCB-265 > URL: https://issues.apache.org/jira/browse/SCB-265 > Project: Apache ServiceComb > Issue Type: New Feature > Components: Java-Chassis >Reporter: wujimin >Assignee: wujimin >Priority: Major > Fix For: java-chassis-1.0.0-m2 > > > As a developer, I want to use generic as my input parameter or response type. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-271) trace solution support reactive mode
[ https://issues.apache.org/jira/browse/SCB-271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yang Bo updated SCB-271: Fix Version/s: java-chassis-1.0.0-m2 > trace solution support reactive mode > > > Key: SCB-271 > URL: https://issues.apache.org/jira/browse/SCB-271 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Java-Chassis >Reporter: wujimin >Assignee: wujimin >Priority: Major > Fix For: java-chassis-1.0.0-m2 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-274) As the Configuration support of Apollo and Configuration Center are quite similar, it doesn't make sense that we put these two module into different places and have differe
[ https://issues.apache.org/jira/browse/SCB-274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yang Bo updated SCB-274: Fix Version/s: java-chassis-1.0.0-m1 > As the Configuration support of Apollo and Configuration Center are quite > similar, it doesn't make sense that we put these two module into different > places and have different configuration codes. > > > Key: SCB-274 > URL: https://issues.apache.org/jira/browse/SCB-274 > Project: Apache ServiceComb > Issue Type: Task > Components: Java-Chassis >Reporter: Bo Li >Priority: Major > Fix For: java-chassis-1.0.0-m1 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-275) [pack] retry compensation on failure/timeout/crash
[ https://issues.apache.org/jira/browse/SCB-275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yang Bo updated SCB-275: Fix Version/s: saga-0.2.0 > [pack] retry compensation on failure/timeout/crash > -- > > Key: SCB-275 > URL: https://issues.apache.org/jira/browse/SCB-275 > Project: Apache ServiceComb > Issue Type: New Feature > Components: Saga >Reporter: Yin Xiang >Priority: Major > Fix For: saga-0.2.0 > > > when omega is unreachable, we may not receive TxCompensatedEvent. > in such case, we have to ask omega to retry on timeout or on omega > disconnected (alpha needs some mechanism to detect connection disruption). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-277) [pack] concurrent event processing issue
[ https://issues.apache.org/jira/browse/SCB-277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yang Bo updated SCB-277: Fix Version/s: saga-0.2.0 > [pack] concurrent event processing issue > > > Key: SCB-277 > URL: https://issues.apache.org/jira/browse/SCB-277 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Saga >Reporter: Yin Xiang >Priority: Minor > Fix For: saga-0.2.0 > > > currently, when alpha is down, it starts from the first event till the last > on restart. > multiple alphas may process the same event at the same time, which results in > concurrent update errors when persisting events as commands. it may not > affect correctness, but does leave warning logs. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-279) As a developer, I need to build edge service to open my microservices to the external users
[ https://issues.apache.org/jira/browse/SCB-279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yang Bo updated SCB-279: Fix Version/s: java-chassis-1.0.0-m2 > As a developer, I need to build edge service to open my microservices to the > external users > --- > > Key: SCB-279 > URL: https://issues.apache.org/jira/browse/SCB-279 > Project: Apache ServiceComb > Issue Type: New Feature > Components: Java-Chassis >Reporter: wujimin >Assignee: wujimin >Priority: Major > Fix For: java-chassis-1.0.0-m2 > > > move not finished task from https://servicecomb.atlassian.net/browse/JAV-350 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-281) published operation depend on configuration
[ https://issues.apache.org/jira/browse/SCB-281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yang Bo updated SCB-281: Fix Version/s: java-chassis-1.0.0-m2 > published operation depend on configuration > --- > > Key: SCB-281 > URL: https://issues.apache.org/jira/browse/SCB-281 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Java-Chassis >Reporter: wujimin >Assignee: wujimin >Priority: Major > Fix For: java-chassis-1.0.0-m2 > > > in real world, not all microservice's operation is published out to edge. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-282) delete and recreate same microservice version
[ https://issues.apache.org/jira/browse/SCB-282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yang Bo updated SCB-282: Fix Version/s: java-chassis-1.0.0-m2 > delete and recreate same microservice version > - > > Key: SCB-282 > URL: https://issues.apache.org/jira/browse/SCB-282 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Java-Chassis >Reporter: wujimin >Assignee: wujimin >Priority: Major > Fix For: java-chassis-1.0.0-m2 > > > schemas maybe changed. > edge must use the recreated meta, not the old meta. > microservice has a "timestamp" property to indicate when this microservice > created > sdk's Microservice class missed this property. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-280) edge service support trace
[ https://issues.apache.org/jira/browse/SCB-280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yang Bo updated SCB-280: Fix Version/s: java-chassis-1.0.0-m2 > edge service support trace > --- > > Key: SCB-280 > URL: https://issues.apache.org/jira/browse/SCB-280 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Java-Chassis >Reporter: wujimin >Assignee: wujimin >Priority: Major > Fix For: java-chassis-1.0.0-m2 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-283) removed deleted microservice version from appManager
[ https://issues.apache.org/jira/browse/SCB-283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yang Bo updated SCB-283: Fix Version/s: java-chassis-1.0.0-m2 > removed deleted microservice version from appManager > > > Key: SCB-283 > URL: https://issues.apache.org/jira/browse/SCB-283 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Java-Chassis >Reporter: wujimin >Assignee: wujimin >Priority: Major > Fix For: java-chassis-1.0.0-m2 > > > how can sdk know when a microservice version deleted? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-284) how can edge service know a microservice meta changed?
[ https://issues.apache.org/jira/browse/SCB-284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yang Bo updated SCB-284: Fix Version/s: java-chassis-1.0.0-m2 > how can edge service know a microservice meta changed? > -- > > Key: SCB-284 > URL: https://issues.apache.org/jira/browse/SCB-284 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Java-Chassis >Reporter: wujimin >Assignee: wujimin >Priority: Major > Fix For: java-chassis-1.0.0-m2 > > > in develop mode, schemas will allowed to be changed, how can edge know when > this happened? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-285) consumer cache schemas
[ https://issues.apache.org/jira/browse/SCB-285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yang Bo updated SCB-285: Fix Version/s: java-chassis-1.0.0-m2 > consumer cache schemas > -- > > Key: SCB-285 > URL: https://issues.apache.org/jira/browse/SCB-285 > Project: Apache ServiceComb > Issue Type: New Feature > Components: Java-Chassis >Reporter: wujimin >Assignee: wujimin >Priority: Major > Fix For: java-chassis-1.0.0-m2 > > > Given: > consumer init. > > When: > consumer find schema. > Then: > 1.if deployed schema in classpath, then use it directly > 2.if configed cache directory and have cached schema, the use it directly > 3.get schema from service center, if configed cache directory, then save to > schema cache directory -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-287) serialize or deserialize by contract in highway transport
[ https://issues.apache.org/jira/browse/SCB-287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yang Bo updated SCB-287: Fix Version/s: java-chassis-1.0.0-m2 > serialize or deserialize by contract in highway transport > - > > Key: SCB-287 > URL: https://issues.apache.org/jira/browse/SCB-287 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Java-Chassis >Reporter: wujimin >Assignee: wujimin >Priority: Major > Fix For: java-chassis-1.0.0-m2 > > > auto ignore properties not in contract, not depend on protoStuff annotation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-286) As a developer, I want to define a object and hide some properties in it to controll the interface publish
[ https://issues.apache.org/jira/browse/SCB-286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yang Bo updated SCB-286: Fix Version/s: java-chassis-1.0.0-m2 > As a developer, I want to define a object and hide some properties in it to > controll the interface publish > --- > > Key: SCB-286 > URL: https://issues.apache.org/jira/browse/SCB-286 > Project: Apache ServiceComb > Issue Type: New Feature > Components: Java-Chassis >Reporter: wujimin >Assignee: wujimin >Priority: Major > Fix For: java-chassis-1.0.0-m2 > > > by using io.swagger.annotations.ApiModelProperty.hidden(), swagger generator > will ignore the property. > but when serialize or deserialize, depend on different annotation in > different tranport. > it's not good. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-288) serialize or deserialize by contract in rest transport
[ https://issues.apache.org/jira/browse/SCB-288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yang Bo updated SCB-288: Fix Version/s: java-chassis-1.0.0-m2 > serialize or deserialize by contract in rest transport > -- > > Key: SCB-288 > URL: https://issues.apache.org/jira/browse/SCB-288 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Java-Chassis >Reporter: wujimin >Assignee: wujimin >Priority: Major > Fix For: java-chassis-1.0.0-m2 > > > auto ignore properties not in contract, not depend on JsonIgnore annotation -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-289) support fiber thread to make sync code run as async logic
[ https://issues.apache.org/jira/browse/SCB-289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yang Bo updated SCB-289: Fix Version/s: java-chassis-1.0.0-m2 > support fiber thread to make sync code run as async logic > - > > Key: SCB-289 > URL: https://issues.apache.org/jira/browse/SCB-289 > Project: Apache ServiceComb > Issue Type: New Feature > Components: Java-Chassis >Reporter: wujimin >Priority: Major > Fix For: java-chassis-1.0.0-m2 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
