I would argue against making interfaces for all your DAOs unless you
know up front that you will be creating multiple implementations. So
long as you don't make any of the methods on your DAOs static, it is
an easy matter to extract interfaces from them at a later point, when
and if you need to d
Yep it is a good practice. Usually u should have an interface and several dao
implementing that interface with a factory, so u can change your database
implementation without having to change the whole code.
You can subclass dao too if u like even if i prefer to use an interface.
Bye
F.
Sun Cert
2 matches
Mail list logo
