That is no problem. I hope the situation is not too bad for you. How does the stateful nature of SCXML fit into the ESB model?
Paul On 11 May 2014 12:48, Dmitry Lukyanov <[email protected]> wrote: > > Hello, > > Sorry for the long delay. It's because of the situation in Ukraine. > I've collected some information about our SCXML implementation. > > Regards, > Dmitry > > > --- Original message --- > From: Dmitry Lukyanov <[email protected]> > Date: 06 December 2013, 00:27:29 > > > Sanjiva, > > We already did implementation of scxml. > We've integrated it into esb as kind of extension.. > Also we have created a really large process based on scxml > that starts from application on the interned and ends with product > delivery to customer. > The process fully described with state machine and executed by engine. > > I can describe the implementation, use cases, data/message access, etc. > > Dmitry > > --- Original message --- > From: Sanjiva Weerawarana <[email protected]> > Date: 02 December 2013, 15:47:12 > > > Dmitry this is something that I've been thinking of for a while .. a > state machine programming model to implement business logic. I'd like to > try to crack this nut in our platform next year. > > Here's a research paper from IBM that provides a great start: > http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.87.2226&rep=rep1&type=pdf > . > > If you'd like to help design / implement that's greatly welcome! > > Sanjiva. > > > On Thu, Nov 28, 2013 at 2:19 PM, Dmitry Lukyanov <[email protected]>wrote: > > Hi All, > > I'm working in a Ukrainian Bank and we are using wso2esb for integration. > I just want to share the idea: SCXML as Module/Mediator for esb. > http://en.wikipedia.org/wiki/SCXML > > The idea is to have something like business processes services. > For example a PaymentOrder service : > > operation createPayment-> state created > state created -> operation confirmPayment -> state confirmed > state created -> operation cancelPayment -> state cancelled > > each state could have onEntry handler (java code called or it could be esb > sequence) > transition could be > conditional (xpath expression) > unconditional (default transition) > and could be triggered by service operation > > Each PaymentOrder instance is actually an XML that enriched > with each operation call and onEntry handlers. > > I understand, that we can use the wso2bps > > - Long running stateful processes > > > But BPEL is quite complex to business people and even for developers, > and SCXML is really simple and easy to understand. > > > > -- > Regards, > Dmitry > > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > > > > -- > Sanjiva Weerawarana, Ph.D. > Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/ > email: [email protected]; office: +1 650 745 4499 x5700; cell: +94 77 787 > 6880 | +1 650 265 8311 > blog: http://sanjiva.weerawarana.org/ > Lean . Enterprise . Middleware > > _______________________________________________ > Architecture mailing > [email protected]https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > > > -- Regards, Dmitry > > > > -- > Regards, > Dmitry > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Paul Fremantle CTO and Co-Founder, WSO2 OASIS WS-RX TC Co-chair, Apache Member UK: +44 207 096 0336 US: +1 646 595 7614 blog: http://pzf.fremantle.org twitter.com/pzfreo [email protected] wso2.com Lean Enterprise Middleware Disclaimer: This communication may contain privileged or other confidential information and is intended exclusively for the addressee/s. If you are not the intended recipient/s, or believe that you may have received this communication in error, please reply to the sender indicating that fact and delete the copy you received and in addition, you should not print, copy, retransmit, disseminate, or otherwise use the information contained in this communication. Internet communications cannot be guaranteed to be timely, secure, error or virus-free. The sender does not accept liability for any errors or omissions.
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
