On Saturday 01 November 2003 12:39, Niclas Hedhman wrote: > On Saturday 01 November 2003 19:01, Alexis Agahi wrote: > > Why not; good idea, but I dont know if PersistenceManager is a classical > > component, would it be able to deal with new component lifecycle? > > > > I mean when a lookup is performed on persistenceManager it should respect > > component dependency, and all lifecycle stage (including persistence > > stuff). > > > > If a compenent can handle such features, then no problem. > > Huh??? > > You are envisioning Persisted components... I have a problem seeing this as > natural thing. I see components having smaller artefacts (value objects of > some kind) that they can store away.
This is maybe because I'm trying to consider the component as EJB/CMP. > Can you give an example of a component that you would like to see to be > persisted? Huh ?? :)) Anything that need to have persistent data. For me a compenent is an object like any other, except it features lifecycle interfaces. So I'm trying to imagine if a component could handle persistence lifecycle interface. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
