> From: Marcus Crafter [mailto:[EMAIL PROTECTED]] > > On Mon, Jul 08, 2002 at 03:50:35PM -0400, Berin Loritsch wrote: > > Enclosed below is the interface for a new proposed lifecycle > > interface. I want to test it out with Fortress before committing to > > anything yet. However, it would allow a component to save a working > > set of data and it's current Configuration. It is meant for > > components that want to keep track of certain information > to help them > > in their decision process. I don't really have any abstraction for > > data serialization because it is very component specific. > > > > I think this version is better and more complete than the > previous one > > I had. I am open to observations, thoughts, etc. > > The interface seems quite similar to > java.io.Serializable - other than > saving the Configuration data in a separate object, what > differentiates Persistable from Serializable ?
Integration with the lifecycle. I would love to come up with something a little better, but I'm not sure what the best way to do it is. Perhaps allow the use of Parameters or Configuration? -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
