This week's book giveaway is in the Clojure forum.
We're giving away four copies of Clojure in Action and have Amit Rathore and Francis Avila on-line!
See this thread for details.
Win a copy of Clojure in Action this week in the Clojure forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

DB Interface and implementation.

 
Pankaja Bansal
Greenhorn
Posts: 19
  • 0
  • Mark post as helpful
  • send pies
  • 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
 
Eiji Seki
Ranch Hand
Posts: 88
  • 0
  • Mark post as helpful
  • send pies
  • 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.
 
I agree. Here's the link: http://aspose.com/file-tools
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic