One more thing ,
I think we can have a set of pre-defined phases and provide ability to
chose set of them for a given resource. Then in registry.xml we define
all the available lifecycle phases and add an ability to define them
from the UI.
Thanks
Deepal
Hi all,
Now we have full support resource copy and rename we can implement
resource lifecycle management. But we need to think how we are going
to do that , and we need to find out what are the phases we are going
to have in our lifecycle management.
So I am thinking to implement something similar to SVN branching as a
way of lifecycle handling , for example when going from QA to
production there will be new branch created for the production phase ,
and it will get a new URL so that we can set the permission as well.
When it come to implementation are we going to add a new method into
Registry interface or are we going to introduce new class to handle
the lifecycle. I would rather like to come up with a new class for
lifecycle (LifeCycleManger) and separate tab in the GUI as well.
One other thing we need to have is custom code running support when a
resource state changes. Say someone tries to move a Resource from QA
phase to production phase then there should be some set of
pre-conditions and post conditions so we need to have the support for
them as well. This is somewhat similar to media type handling we have
in the current implementation.
I think we have to have a section in registry.xml for lifecycle
handling , and which may contains configurations such as ;
- What are the phases in the lifecycle (Development , QA ,Production
and etc...) , and which should be configurable as well
- A way to register handlers for state changes
- Associate URL name (suffix) for the phase
- Permission based on the lifecycle, (who can change the resource
lifecycle states. )
Thoughts ... ?
Thanks
Deepal
_______________________________________________
Registry-dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/registry-dev
