We unfortunately don't have any real samples of using the save interceptor.  Several of the security samples use a simple save interceptor, but likely wouldn't help much.   At the moment the best example of a save interceptor is in the API documentation:  http://drc.ideablade.com/ApiDocumentation/webframe.html?IdeaBlade.EntityModel.Server~IdeaBlade.EntityModel.Server.EntityServerSaveInterceptor.html

 

Time ago a feature request to saveinterceptor per class was placed

Do you have a timeline to implement this?

 

Do you have an application demo (VS solution in WPF) using save interceptors?

thanks.

 

thanks Kim.

 

In your experience developing LOB APPS with devforce using "DevForce main funcionality" where place the business logic? in the client side or in the server side? i.e. I want to place the business logic in the RSM to avoid to deploy dlls to the client because in such case i should obfuscate that dlls moreover i should send more info through the net (because in the process logic i create new objects)

but i want to know your opinion.

 

thanks and excuse my bad english.

 

 

Although the methods are not discoverable and not strongly typed, you don't need to group the methods into a single EntityManager - they can be called from any EntityManager.  Most of our customers "hide" these methods from within repository methods, so that the calling code knows nothing about the actual invocation.

 var serverMethod = new ServerMethodDelegate(ServerMethods.GetNumberOfOrders);
 return (int)_entityManager.InvokeServerMethod(serverMethod, startDate, endDate);

since the client developer cannot discover the server method contracts.

 

 

 

Do you have a VS solution (server side, client side) as example to using server methods with ECS using Delegate?

thanks in advanced.

I have DevForce. After reading the article in http://msdn.microsoft.com/en-us/magazine/ee335715.aspx i´m reflexive about the DevForce suggested architecture. I want to have a service layer that get the input (an entity) and coordinates a serie of domain objects to make one operation (May be many objects was updates some more inserted etc). With DevForce i think (may be wrong) that this service layer should be in the client side and then execute Context.Save.

I want to build an hybrid architecture where the read queries use DevForce with POCOS and the update queries use wcf services, the purpose to this is having the service layer server side (i know the server methods of devforce but i don´t like them). Can you gime some advice to this architecture?

thanks.