Granny's Programming Pearls
"inside of every large program is a small program struggling to get out"
JavaRanch.com/granny.jsp
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Liutauras Vilda
  • Bear Bibeault
  • Paul Clapham
  • Jeanne Boyarsky
Sheriffs:
  • Junilu Lacar
  • Knute Snortum
  • Henry Wong
Saloon Keepers:
  • Ron McLeod
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
Bartenders:
  • Frits Walraven
  • Joe Ess
  • salvin francis

DAO or Service?

 
Ranch Hand
Posts: 332
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I'm doing B&S. I see, that some ranchers chose to create a simple interface for clients and gave it a name e.g. ContractorService.

My dilema currently is, whether I should name my interface also in this way, e.g. "ContractorService" or stay with "ContractorDAO".

My reasoning is, that what this interface really does, is providing access to data source (local or remote), where transfer object is Contractor.

I guess, that Service is probably doing something more in real world, but in case of our assignment I don't see difference.

What are the essential differences when I'm calling something Service?

Thank you.
 
Greenhorn
Posts: 10
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Well, in my B&S assingment there is a DB interface which I have to implement using a class called Data.

DB declares some methods like get(recNo), search(...), delete(recNo), ...
all those tasks a usually the concern of a DAO.

In a 3 tier architecture you should now create a layer (the service or business layer) on top of the DAO (DB, Data, ...) which, in very simple cases just delegates to the DAO.
This service usually combines the primitive methods of DAOs to implement the business needs. Checking if a record is available before booking it could be such a task.
 
Would you turn that thing down? I'm controlling a mind here! Look ... look at the tiny ad ...
Java file APIs (DOC, XLS, PDF, and many more)
https://products.aspose.com/total/java
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!