Peter Donald wrote:
> At 08:01 AM 6/14/2002 +0200, you wrote:
>
>> I think we need to address the need for an easy system to enhance the
>> Lifecycle.
>> In James we will possibly need the Mailet interface in the lifecycle.
>
>
> I dunno - Phoenix has had Block/Application Listener has had equivelent
> interface for a long time (we have termed them structural interfaces)
> now without messing up lifeccycle process.
>
> Feature added services ala Saveable/Exportable/etc should occur
> inbetween startup and shutdown so no need to mess up lifecycle for that
> either.
:-?
I need the Container to call save() on the components at any time it is
needed.
For me, each Component is an instance of an app, and since the system
does autosaving, it needs to ask the Component to save when needed.
What does this have to do with startup-shutdown?
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
