Hi Manu, In an offline discussion with Ayesha, I learnt the following regarding the defaultLifecycleEnabled property:
- defaultLifecycleEnabled: *true *This property needs to be set to "true" in the asset extension (asset.js) when a user wants to attach a lifecycle to an asset type. This is in the event that the user has not already defined a lifecycle when creating the asset type. - defaultLifecycleEnabled: false This property needs to be set to "false" when the user has defined a lifecycle when creating the asset type. Based on the latter mentioned, ES considers the lifecycle defined in the asset extension (asset.js) as the default lifecycle for the asset type. However, GREG refers to the lifecycle defined in the RXT as the default lifecycle [1]. Is it really necessary to deviate from the concept that GREG uses? This can end-up confusing the user. As the initial impression that the user gets when seeing the "defaultLifecycleEnabled" property is that if this property is set to true, the lifecycle defined in the RXT will be considered, and if we set this property to false, the lifecycle defined in the asset extension will be considered. However, ES has been designed to work wise versa, which is confusing, because we are telling the user to consider a lifecycle defined in an extension as the default as opposed to the lifecycle that is defined in the RXT, which is the root source for an asset type. I do understand that it is not mandatory to define a lifecycle in the RXT. However, it might be better to change the current ES implementation, so that "defaultLifecycleEnabled: true" refers to the lifecycle in the RXT. WDYT? [1] https://docs.wso2.com/display/Governance460/Governance+Artifacts+Configuration+Model+Elements#GovernanceArtifactsConfigurationModelElements-ThelifecycleElement Regards, Mariangela *Mariangela Hills* Senior Technical Writer - WSO2, Inc. http://wso2.com Committer and PMC member - Apache Stratos email:mariang...@wso2.com | mobile: +94 773 500185
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
