• 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 Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

DB Interface and implementation.

 
Greenhorn
Posts: 19
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator


Your data access class must be called "Data.java", must be in a package called "suncertify.db", and must implement the following interface:

package suncertify.db;
public interface DB
{.... }




Since the DB interface here contains lock and unlock mechanism, I created a wrapper class around my Data.java class which locks, performs the operation and unlocks the object. Since the connection could be local or remote, my client would require to deal with an interface. My question now is, is it mandatory to use this given interface "DB.java" for clients use or can I create another interface which my wrapper class would implement and this interface would actually be passed to client for all its operations.

I dont want client to be handling lock and unlock processes and all the client should be bothered of is operations on the database. Can my approach fail automatic test because I'll be using another interface apart from DB for the client to access data ?

Please let me know your views.

Pb
 
Ranch Hand
Posts: 88
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Well, I guess you can use your own interface, since the spec only requires your class to implement it, not you to use it.
Probably they will use it to run your data layer on a automated evaluation.
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
reply
    Bookmark Topic Watch Topic
  • New Topic