This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
I got the B&S assignment and I'm not quite sure if the supplied DB-Interface shall also be the interface for communication between client and server. Or do I have the choice to introduce a business layer on the server so that DB acts as a DAO?
The latter case would make it possible to send value objects over the network and the client wouldn't need to handle string arrays.
It seems a lot of discussions on this issue have taken place on this forum. Some people seem to interpret the instructions as if they are obliged to use the supplied interface as the business interface which must also be exposed to the clients. Personally, I have never found the reason for this arguing in my instructions, so I just have a very simple business interface which only has the methods book and search.
I have the same opinion from Rinke, and I have a package with my business interface, with its own exceptions, as an adapter from the DBClient interface supplied by Sun (in my case my assignment is the URLyBird) to my new DBBusinessServices interface. It has only the reserveRoom, cancelRoomReservation, searchRoomsByCriteria and searchAllRooms methods.
SCJP5(93%), SCJD(in progress...), SCEA(not started yet...)