Our architecture is currently in this way (in .NET 2.0):
- Data/entity classes are non-serializable
- lots of code in getters/setters in several properties of entity classes (core business validations/business data refresh etc.)
- logic behind getters/setters would also access database.
- modifying a value in a setter would reflect several other properties/subcollections of the current class
- one "Save" method updates the current in-memory object (along with all subcollections) to database
- validations are handled as collection from the same class (and would automatically refresh based on getter/setter)
While I understand that there are several problems in the above architecture, we would like to have a stateless architecture to be designed/developed using Entity Framework, WCF/RIA etc.
The problem is with the logic behind getters/setters. What is going to be the best way to accomplish these using EF and WCF/RIA?
thanks for all of your advice