saoj wrote:public interface UserDAO { public User loadById(int id) throws Exception; public int insert(User user) throws Exception; public void update(User user) throws Exception; public void delete(User user) throws Exception; public User loadByUsername(String username) throws Exception; public User loadByEmail(String email) throws Exception; public List searchUsersByName(List keywords, boolean and) throws Exception; public List searchUsersByName(List keywords, boolean and, int max) throws Exception; }
1) Posso considerar essa interface como respositório?

2) Como ficaria um repositorio então nesse meu caso?

Rafaelprp wrote:onde acho documentação da sun falando sobre esses padrões de nomes ?

Rafaelprp wrote:
e no caso, isso aqui estaria errado ?? Lá ele utiliza a nomeclatura DAO na interface...

Rafaelprp wrote:
Tá parecendo aquele velho papo que no mundo java existem vários nomes para a mesma coisa...

"Phillip Calçado" wrote:
Re: [domaindrivendesign] Farewell to Repositories (I think)

The main thing to keep in mind while working with Repositories is that
they're a domain concept, while a DAO or any other Mapper between
objects and tables aren't. The domain classes knows that repositories
are where business objects instances remain. As a business concept it
can and will be handled, received as a parameter, etc. by those
business domain classes like services and entities.

A DAO doesn't fit in a Repositories place directly, this would break
layered archtiecture of a application, but generally a Repository is
just something that when invoked will call a DAO.

To avoide the tortures of creating a brinless delegator as a
Repository you can use the Dependency Inversion principle, by Uncle
Bob, and make Repository an interface implemented by the DAO class.
This way your domain classes won't end up dependent on infrastructures
classes (like DAOs) while you avoid creating Repository classes that
acts just like delegators.

I've used this approach more than once. In a recent project I've used
this Dao<<implements>>Repository strategy and suddenly was requested
that before checking the database I'd have to first check a enterprise
search engine (something like google appliances or a dedicated Lucene
server). I used to have:
Domain Object --<<depends>>--> Repository <--<<implements>>-- DAO
And changed to:
Domain Object --<<depends>>--> Repository Repository <--<<implements>>-- RepositoryImpl --<<depends>>--> DatabaseDao--<<depends>>-->SearchEngineDao

The RepositoryImpl was the class responsible for looking for the
instance persisted in one of the two deta repositories. The domain
classes that just relied on the Repository concept, not its
implementation, weren't affected.

cheers

Rafaelprp wrote:Tá parecendo aquele velho papo que no mundo java existem vários nomes para a mesma coisa...

Fabio Kung wrote:

saoj wrote:public interface UserDAO { public User loadById(int id) throws Exception; public int insert(User user) throws Exception; public void update(User user) throws Exception; public void delete(User user) throws Exception; public User loadByUsername(String username) throws Exception; public User loadByEmail(String email) throws Exception; public List searchUsersByName(List keywords, boolean and) throws Exception; public List searchUsersByName(List keywords, boolean and, int max) throws Exception; }
1) Posso considerar essa interface como respositório?

. . . e aí sim renomearia para UserRepository.

pcalcado wrote:Sim, Sérgio, pode chamar de Repositório.