Re: [DISCUSS]Add a local or embedded interface to call Saga

2018-08-22 Thread Willem Jiang
I just created a new issue[1] for this new feature, please feel free to create sub task to track you task. [1]https://issues.apache.org/jira/browse/SCB-864 Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Wed, Aug 22, 2018 at 5:07 PM, 新道场开张了 wrote: > Yes, it is relate to the Operation

Re:[DISCUSS]Add a local or embedded interface to call Saga

2018-08-22 Thread ????????????
Yes, it is relate to the Operation that Saga already defined in saga-core. I just want to add a new String named TYPE_SQL like TYPE_REST and TYPE_NOP. The TYPE_SQL may be used by JsonSagaRequest interface to let Jackson find the implement class based on 'type' property. Some questions about

Re: [DISCUSS]Add a local or embedded interface to call Saga

2018-08-22 Thread Willem Jiang
Just a quick question about the Operation's TYPE_SQL? I'm not sure if it is relate to the Operation that Saga already defined. BTW, you can create a JIRA and attached the UML design document to it. Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Wed, Aug 22, 2018 at 3:51 PM, 新道场开张了

Re: [DISCUSS]Add a local or embedded interface to call Saga

2018-08-22 Thread Zheng Feng
Nice work and I think you could raise the JIRA on https://issues.apache.org/jira/browse/SCB for this new feature. Good luck with the implementation ! 2018-08-22 15:49 GMT+08:00 新道场开张了 : > SCSagaSQLFormatDesign.png > > > This picture is my design for embedded interface to call Saga. > In the

Re:[DISCUSS]Add a local or embedded interface to call Saga

2018-08-22 Thread ????????????
sorry, the image link seems to be invalid. https://raw.githubusercontent.com/KomachiSion/incubator-servicecomb-saga/share/docs/static_files/SCSagaDesign.png -- -- ??: ""; : 2018??8??22??(??) 3:49 ??: "dev"; :

Re:[DISCUSS]Add a local or embedded interface to call Saga

2018-08-22 Thread ????????????
SCSagaSQLFormatDesign.png This picture is my design for embedded interface to call Saga. In the design, we need to extend TYPE_SQL=sql in Operation interface and JsonSubTypes in JsonSagaRequest interface. And we need to add some classes to match the new json we defined before. we also can reuse

Re?? [DISCUSS]Add a local or embedded interface to call Saga

2018-08-20 Thread ????????????
sorry, the picture is a simple UML of SQLTransport https://github.com/KomachiSion/incubator-servicecomb-saga/blob/master/docs/static_files/Transport.jpg -- -- ??: "Willem Jiang"; : 2018??8??21??(??) 10:20 ??: "dev"; : Re:

Re: [DISCUSS]Add a local or embedded interface to call Saga

2018-08-20 Thread Willem Jiang
Yeah, the json format of SQL Transport sounds good. As we normally use the text in the mailing list, so please draw asiis picture or put a permanent link in the mail for us to review. Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Tue, Aug 21, 2018 at 10:11 AM, 新道场开张了 wrote: > I

RE?? [DISCUSS]Add a local or embedded interface to call Saga

2018-08-20 Thread ????????????
I think we can extend Transport interface to a new interface named SQLTransport. the SQLTransport also include 'with' function, but the parameters only requires datasource/serviceName, sql and parameters. Users can decide how to execute the sql of the datasource/serviceName in their own

Re: [DISCUSS]Add a local or embedded interface to call Saga

2018-08-20 Thread Zheng Feng
Thanks Willem and it is a good point here. Also I'm interesting how it could be used in the local or the embedded interface ? I wonder if you can consider the ACID transaction in this situation. The Saga in my options could be more used for the distributed environment. Regard, Amos 2018-08-20

Re: [DISCUSS]Add a local or embedded interface to call Saga

2018-08-20 Thread Willem Jiang
the saga-core has a transport[1] interface which could be used for the purpose, now it just have the Restful implementation. If you want to implement a RPC or some local method, you can just implement the transport interface. As the saga-core using json for the invocation, you need to updated the