Re: [Figleaf-developer] Questions regarding ObjectManager

[<sam...@ma...>]

Quoting Greg Steckman <ste...@on...>:



> >
> >We really need to consider if we require a PersistenceStrategy - e.g. save
> on
> >edit (e.g. call a set and its persisted ala Entity beans) or save on
> specific
> >call (hit the save button). This can probably wait till 0.2 or later, but
> we
> >need to fix on a default strategy for this version.
> >
> >  
> >
> For now I put in a save button on the Form view. I think this meshes 
> well with validation, because when the user wants to save, the object 
> can be validated once and if it fails an error presented. I can imagine 
> situations where an object needs to be validated after all its data is 
> entered, rather than after each field is changed.

Agreed - for this version at least it's a sensible approach. It also meshes well
with the persistence implementations we are looking at providing (Hibernate,
Prevalyer etc).

> >Do we want to implement our own lazy loading mechanism, or can we just
> leave
> >this down to whichever persistence mechanism we want? Thinking about the UI,
> its
> >up to specific implementations as to what objects they want to load at any
> one
> >time - one UI when loading an object may want just that object, another
> might
> >want to load all members of that object.
> >
> I think when we get to implementing remoting, we'll have to put in some 
> type of lazy loading and caching implementation. That implementation 
> should then be usable on the server or remote end. It's certainly 
> something I don't want to start implementing at this point yet. Since 
> I've used Hibernate, I think there will be some issues with how it does 
> lazy loading and the requirement to keep sessions open. Also there is 
> the case of needing to introspect to make informative objects when 
> lazily loaded. If our container doesn't control the loading, I don't 
> know how to know when to introspect the object.

Sounds sensible - lets worry about it when it happens


sam
http://www.magpiebrain.com/