Hi, > How about an Interface PersistableBlock that implemented the following > methods :- > > Object persist(); > void unPersist(Object persistedForm); > > Phoenix, on shutdown, could persist the block. If built-in, the > unPersist method would come just before initialize() in terms of > lifecycle;
-1 ... I don't see this functionality as a Kernel service! Do you really need to persist Blocks or just Components? > As a slight alternative, it could be a Cornerstone interface and a > separate block (with defautl impl). That block could, on stop(), invoke > the persist() method it it's dependancy. It could similarly invoke > unPersist for on start(). That default block could take a number of > configurations, including one that had a cron based automatic > persistence scheme. Once the access to Phoenix level services is implemented (Deployer, ConfigurationRepository ...) then maybe you can use the ObjectStore to store block instances and later on load & add them to the Kernel. Mircea -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
