Hi Eranda,

-1 for a concept of an explicit state specific lifecycle.

Lets take your example. Say we have both ES-LC and Dev-LC. Ideally, there
will be two independent lifecycles. There needs to be some implementation
or configuration that will tie these two lifecycles together. For example,
like there are some checklist rules that need to be statisfied for being
able to Promote from X to Y, you might also need to satisfy some other
conditions in different lifecycles in order retain your existing state or
promote from current to next and vice versa.

So, the user can define/extend how the lifecycles depends on each other,
but from the framework level you can have two or more completely
independent lifecycles.

Thanks,
Senaka.

On Fri, Dec 12, 2014 at 1:21 AM, Eranda Sooriyabandara <era...@wso2.com>
wrote:

> @Sagara, Senaka, Shazni,
>
> Here I am bit worried about the lifecycle state combinations we are
> getting.
> Let's take the example of Service. In service lifecycle we have
> Development, Test, Production and then we have a ES lifecycle which
> contains Created, Published, Retired. Think we associate both lifecycle to
> a service where we need to promote the service to the service store while
> keep it in the development. We can do it by changing the ES lifecycle to
> published. Then we promoting the service lifecycle to QA and still we see
> ES lifecycle is in published state which is bit confusing. Please correct
> me if I am wrong.
>
> If you look closely to the use case provided by Sagara, Service lifecycle
> is the main lifecycle and the ES lifecycle is a state specific lifecycle
> where when we promoting Dev to Test we should not transfer the state of ES
> lifecycle. So I hope we should have a main lifecycle and we should be able
> to define state specific lifecycles where we can select existing
> lifecycles.
> WDYT?
>
> thanks
> Eranda
>
>
>


-- 


*[image: http://wso2.com] <http://wso2.com>Senaka Fernando*
Solutions Architect; 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: +44 782 741 1966Linked-In: http://linkedin.com/in/senakafernando
<http://linkedin.com/in/senakafernando>*Lean . Enterprise . Middleware
_______________________________________________
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Reply via email to