File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
The moose likes Developer Certification (SCJD/OCMJD) and the fly likes Design of the DB part Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Certification » Developer Certification (SCJD/OCMJD)
Bookmark "Design of the DB part" Watch "Design of the DB part" New topic

Design of the DB part

Geir Morten Hagen
Ranch Hand

Joined: Apr 05, 2002
Posts: 34
I just started the SCJD assignment, and have some questions about the design of the database.
I was thinking of splitting up the data class into two parts; one for the "system" responsibilities, and one for the application spesific responsibilities.
The system part would include functionallity like adding records, deleting records, locking records and so on, while the other part would include the functionality the booking client needs like criteriaFind and bookSeats.
The latter interface will then be used in the rmi-part of the application.
There will be a base Data class which is subclassed by a BookingData class which implements the BookingDataInterface.
These are just some first thoughts about the design. Any comments will be appreciated
And one last question.. I was thinking of letting the Data class issue its own lock request when methods requiring record locking are called from the client. Or do anyone have a good reason why the client should call the lock request instead?
[ April 05, 2002: Message edited by: Geir Morten Hagen ]
I agree. Here's the link:
subject: Design of the DB part
It's not a secret anymore!