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. > >
My only concern would be in creating a new package for this. oaaf.persistable sounds like a persistence mechanism like JDO or Castor or somesuch. Why not just create a PersistableConfiguration w/in oaaf.configuration? -Mark -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
