Hi Nuwan, Amila, If you for a moment think of a Store/Publisher webapp being a resource (just a logical assumption), is this kind of workflow similar to a registry lifecycle? We shouldn't be looking at the configuration model or what it does today, but the functional similarity.
I'm asking these questions to understand whether we should unify the concept of workflow inside the platform to be based on some similar model. Thanks, Senaka. On Thu, Mar 6, 2014 at 11:36 AM, Nuwan Dias <[email protected]> wrote: > From what I understand, a registry lifecycle is always associated to a > registry resource (only). But workflows are plug-points to various UI > actions that you perform on the Store/Publisher webapps. Ex: A user > sign-up, API Subscription, etc. > > Thanks, > NuwanD. > > > On Thu, Mar 6, 2014 at 11:28 AM, Senaka Fernando <[email protected]> wrote: > >> Hi Amila, >> >> How different are these workflow configurations from a registry lifecycle >> configuration? I'm not suggesting that we reuse, but just to understand. >> >> Thanks, >> Senaka. >> >> >> On Thu, Mar 6, 2014 at 11:04 AM, Amila De Silva <[email protected]> wrote: >> >>> Hi, >>> >>> Currently the configuration for Workflow Executors are kept in the >>> api-manager.xml. Due to this design, there'll be a single workflow >>> configuration for an entire deployment and all the tenants have to use the >>> same executors. >>> >>> We are planning to move Workflow Configuration to the registry. A >>> default configuration will be sent with the pack, and it'll get added to >>> the registry when; >>> 1. The pack is first started - (Workflow configuration is created >>> created in the Super Tenant's registry) >>> 2. A new Tenant is Created - (Workflow configuration is created created >>> in the respective Tenant's registry). >>> >>> With this, each tenant will be referring to the configuration stored in >>> their own Registry space. >>> To change the configuration, the Tenant Admin has to log into the admin >>> console and edit the registry resource. >>> >>> -- >>> *Amila De Silva* >>> >>> *Software Engineer* >>> WSO2 Inc. >>> mobile :(+94) 775119302 >>> >>> >>> _______________________________________________ >>> Architecture mailing list >>> [email protected] >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>> >>> >> >> >> -- >> >> >> *[image: http://wso2.com] <http://wso2.com> Senaka Fernando* >> Senior Technical Lead; WSO2 Inc.; http://wso2.com >> >> >> >> * Member; Apache Software Foundation; http://apache.org >> <http://apache.org>E-mail: senaka AT wso2.com <http://wso2.com>**P: +1 >> 408 754 7388 <%2B1%20408%20754%207388>; ext: 51736*; >> >> >> *M: +94 77 322 1818 <%2B94%2077%20322%201818> Linked-In: >> http://linkedin.com/in/senakafernando >> <http://linkedin.com/in/senakafernando>*Lean . Enterprise . Middleware >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > Nuwan Dias > > Senior Software Engineer - WSO2, Inc. http://wso2.com > email : [email protected] > Phone : +94 777 775 729 > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- *[image: http://wso2.com] <http://wso2.com> Senaka Fernando* Senior Technical Lead; WSO2 Inc.; http://wso2.com * Member; Apache Software Foundation; http://apache.org <http://apache.org>E-mail: senaka AT wso2.com <http://wso2.com>**P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 Linked-In: http://linkedin.com/in/senakafernando <http://linkedin.com/in/senakafernando>*Lean . Enterprise . Middleware
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
