[Registry-dev] Resource lifecycle handling

[Deepal Jayasinghe]

> Plus also we need a default lifecycle impl that does nothing (just 
> accepts the change).
Yes, we will have a default lifecycle impl which copies the resource 
from one location to another when we do the lifecycle changes.
>
> How do we manage security? How do I configure who can change lifecycles?
I think that is something we have to decide  , as Glen suggested we can 
associate action for any given life cycle phase and configure security 
based on that.
>
> Can we set properties onto Lifecycle handlers? So in other words can I 
> have a pre-defined lifecycle handler that I parameterize with config 
> properties in the registry.xml?
You mean for all the resource ? , yes that would be a good idea. 
Otherwise user has to configure the resource every time when he wants to 
do the lifecycle handling.
>
>
> Finally is there any way we can script the lifecycle handling? Maybe 
> have a lifecycle handler that calls out to BSF, and I configure it 
> with a simple javascript to do some checking when it gets called. The 
> script would need access to the Registry.
We should , but may be not for the 1.1  :)

Thank you!
Deepal