Hi,

I'm hoping this is possible... is there a standard way to execute a code block in an entity as a pre or post save event in the adapter model?

Given the entity has no reference to the adapter, are there standard pre/post methods that the adapter calls on an entity during an attempt to persist an object that can be customised?

Thanks, Stef

Adapter has in the DataAccessAdapter class OnSaveEntity() and OnSaveEntityComplete methods, which you can override in a derived class of DataAccessAdapter.

For what particular situation do you want to use these methods?

Thanks Otis, The need for this arose because I'd like to use the role object pattern to capture the various roles that a person can belong to. I can't use inheritance as the person may belong to serveral roles e.g. they could be a client and a vendor at the same time. There are also rules defining the compatibilty of roles, for example it is not possible to be a client and a prospect at the same time.

The roles are subobjects of the root person object and implemented using LLBLGens relationships however I'd prefer to provide an interface that doesn't require the user to test for the presence of each object. As the roles are expanded the code gets rather messy. By placing the sub entities into a roles collection I can then perform actions on the collection rather than having to know the subobject structure.

All this leads to the need to update the subobjects from the collection, if necessary, when the root person object is persisted and so I'd like to execute some additional before the adapter saves the object graph.

Cheers, Stef

I think you can solve this by creating a IEntityValidator implementation and set the entity's EntityValidatorToUse property to an instance of that validator. Then simply call Validate() and your validator is called.

Otis wrote:

I think you can solve this by creating a IEntityValidator implementation and set the entity's EntityValidatorToUse property to an instance of that validator. Then simply call Validate() and your validator is called.

Thanks, I'll have a look at this since it is a little neater than my current approach... given the methods you mentioned previously in the DataAccessAdapter I created a simple interface that an entity could implement.

public interface ISaveHooks { void PreSaveHook(); void PostSaveHook(); }

An entity implements this interface is there is additional code to execute before or after the save. The DataAdapter methods mentioned are extended to check whether or not the entityToSave implements this interface and if so the relevant method is called.

Thanks, Stef

That could work as well indeed. You can alter the template for the entities to implement this interface or add the interface to the user code region for additional interfaces