Customer Relationship Management (CRM)
The Technical "Know-How"
DAO Transaction - Consistency and Refactoring
Our view of Data Access Object (DAO) is that of human cardiovascular system, where the blood
circulate and transport nutrients, oxygen to nourish the body. There are different types of blood cells.
The way to present our Transaction DAO is by given an example. Let us say a developer is building a Business
Object (BO) to calculate different interest loan options with different loan packages. The Intelligent
DAO will provide the interest, loan amount and payment options and other functionalities. The developer
would use these DAO services and does all the different loan options. The developer may create a number
of exceptions and errors handlers within the BO. Looking at the code which would be repeated in almost
every Java object and methods are: logs, security, other calls exception (some else code), errors
handler, IO and utilities errors and exceptions, server performance, .. etc. Not mention, that if every
developer would be doing his/her own version of handing these code segment, we definitely have serious
issues. The Transaction DAO would be performing all these common code and handling which would help with
security, consistency, refactoring and elimination of possible errors. Refactoring of Personal DAO,
Transaction DAO would not be require any modification within the developer BO.
Transactional can be subcategorized into Security Information DAO.