Tag Info

New answers tagged

0

I think you might be confused by the term "business" which typically refers to "business logic," or the rules that define the flow of data through a system. From what you described, "business layer" is really the controller in MVC: it describes how the system operates to achieve its goals. Ideally, the model and view would have zero knowledge about each ...


0

When dealing with the data access layer code, you can think of the following: Think of a persister, something that does operations on the data in the underlying persistence layer, such as save, delete, and update operations. POJOs that represent the records in the tables are part of the DAL. Every thing that depends on and queries that layer directly in ...


0

Although it's not a very satisfactory answer, pretty much as soon as you introduce a condition (if, switch, etc.) into your data layer code, you're technically mingling business logic and data access. The reason it's not very satisfying is that this implies that data access code is pretty dumb -- it handles C.R.U.D. behaviors only. That's why ORM emerged ...


0

The PersonDetail class is part of the data access. The service that updates PersonDetail is business logic. Note that, if you don't actually need this separation (i.e. you won't need to transplant the service layer to some other program, independently of the data access), it may not matter (you're coupled to the data layer anyway, due to the presence of ...



Top 50 recent answers are included