DAO pattern

[Alexey J.1001958768]

Hello!

Question addresses primary to object relation mappers users.

Does anyone explain me why business objects shouldn't have a dependency on
the persistent layer (DAO objects).
I want to exclude business logic from a controller and concentrate it into a
business objects. Methods of the business object
must intensively use DAOs. But it violates this dogma.

And question: how could I able to write more complicated business methods
without access to DAO objects?

Thanks.
Sorry for my poor English.

 

[Anzime]

Hello!

Question addresses primary to object relation mappers users.

Does anyone explain me why business objects shouldn't have a dependency on
the persistent layer (DAO objects).

Think about switching databases.

I want to exclude business logic from a controller and concentrate it into a
business objects. Methods of the business object
must intensively use DAOs. But it violates this dogma.

And question: how could I able to write more complicated business methods
without access to DAO objects?

Have your business logic classes call handlers that call DAO classes.
Handlers may contain additional pre/post DAO logic.