More and more I’ve seem the Repository been used as a fancy name for DAOs. It is very common nowadays to have things named Repository that create SQL/HQL/EJBQL queries or deal with database transactions or connections. Only a DAO with a different name.
I thought about posting something about the differences between DAOs and repositories again but I really can’t add anything to the previous post at this time.
The industry seems to be leaning towards accepting this misuse as a default.
e.g. this is Spring’s 2.5 @Repository annotation doco:
“public @interface RepositoryIndicates that an annotated class is a “Repository” (or “DAO”).”
Cheers.
Between all patterns from the DDD the Repository is what brings more confusion for developers, maybe because they think always in DAOs when if speak about persistence!
You write about “business concept” of Repository in previous post…
Could You explain it to me as if I were and idiot what is the difference between:
- classic DAO but just called Repository (ex OrdersRepository instead of OrdersDAO)
- your real Repository
I think that code example would be sufficient - interface and impl for both cases. If You could also add some kind of philosophyical explanation to examples than everything should be clear. But I think that only example can clarify this issue.