This site contains the documentation that is relevant to older WSO2 product versions and offerings.
For the latest WSO2 documentation, visit https://wso2.com/documentation/.

Lifecycle Configuration Model

Owned by Former user (Deleted)
Last updated: Nov 20, 2012 by Former user (Deleted)Version comment
7 min read

The configuration model of the WSO2 Governance Registry lifeCycles gives users the ability to define custom behavior to a registry lifecycle operation. This model is capable of defining the following custom behaviors:

  • Define permissions for each check item
  • Define custom validations for each check item
  • Define a set of check items for each state transition
  • Define permissions for each state transition
  • Define custom validations for each state transition
  • Define programmable executions for each state transition
  • Define custom UIs accepting user input for each state transition

Configuration Model

<aspect class="org.wso2.carbon.governance.registry.extensions.aspects.DefaultLifeCycle" name="">
    <configuration type="">
        <lifecycle>
            <scxml initialstate="" version="1.0" xmlns="http://www.w3.org/2005/07/scxml">
                <state id="">
                    <datamodel>
                        <data name="checkItems">
                            <item forEvent="" name="">
                                <permissions>
                                    <permission roles="">
                                    </permission>
                                </permissions>
                                <validations>
                                    <validation class="" forEvent="">
                                        <parameter name="" value="">
                                        </parameter>
                                    </validation>
                                </validations>
                            </item>
                        </data>
                        <data name="transitionValidation">
                            <validation class="" forEvent="">
                                <parameter name="" value="">
                                </parameter>
                            </validation>
                        </data>
                        <data name="transitionPermission">
                            <permission forEvent="" roles="">
                            </permission>
                        </data>
                        <data name="transitionScripts">
                            <js forEvent="">
                                <console function="">
                                    <script type="text/javascript">
                                    </script>
                                </console>
                                <server function="">
                                    <script type="text/javascript">
                                    </script>
                                </server>
                            </js>
                        </data>
                        <data name="transitionExecution">
                            <execution class="" forEvent="">
                                <parameter name="" value="">
                                </parameter>
                            </execution>
                        </data>
                        <data name="transitionUI">
                            <ui href="" forEvent=""/>
                        </data>
                    </datamodel>
                    <transition event="" target="">
                    </transition>
                </state>
            </scxml>
        </lifecycle>
    </configuration>
</aspect>

For details of each element of the configuration, refer to Lifecycle Configuration Elements.

Â