Hi, i am using self servicing for a web project and have my business layer (BL) for all kinds of data access. i never call the entity properties or methods on gui. there is always the BL in between. The question is; is there a way to proihibit using entity methods on the GUI layer? All create, edit, modify, delete actions are taken care of in BL but one can easily change it on GUI by creating an entity, setting up its properties and calling the built in methods. Is there a way to make sure this wont happen?

thank you -shane

we designed adapter for precisely that situation: persistence is separated from the entity classes. Selfservicing doesn't offer this, so you have to be careful what you're doing, especially with lazy loading.

so can i not do this on gui side if Adapter is used?:

CustomerEntity customer = new CustomerEntity();

customer.CustomerID = "FOO"; customer.CompanyName = "Foo Inc."; customer.Country = "USA";

DataAccessAdapter adapter = new DataAccessAdapter(); adapter.SaveEntity(customer, true);

i dont think i get this part. As long as i have a reference to both projects Adapter creates, isnt it possible to use the code above in GUI also? what is stopping me?

thank you -shane

e106199 wrote:

what is stopping me?

Good practice? No one is stopping you to do such things, the difference is that with the adapter you have an option not to do it.

To prevent this - All you really need to do is make sure your main web project does not have a project reference to the Adapter project.

Ryan

You could also use dependency injection to get an IDataAccessAdapter of your choosing. We are happily targetting both Oracle and SQL Server with the exact same GUI codebase using this strategy.

Nice, Seth!