Meaningless Drivel is fun!
The moose likes Developer Certification (SCJD/OCMJD) and the fly likes B&S Design Decision 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 "B&S Design Decision" Watch "B&S Design Decision" New topic

B&S Design Decision

Dhanasekar Dhakshin

Joined: Jan 19, 2006
Posts: 5
Hi Friends,

Im in Design phase of my B&S assignment. I have some couple of Questions regarding design.

1. I made my as singleton. Is it correct?

2. In my gui i used command design pattern for event handling.
Is it right approach for this assignment.

3. For remote call i plan to use Transfer Object design pattern. I feel it reduce network calls from client.

for example,

Booking a record i'll send a record no and customer id as a single transfer obj to server. server method update the particular record with customer id and it return all the remaining unbooked records as a single transfer obj.

I want to know how ppls handle this.

Please suggest a better solutions . . .

Jeroen T Wenting
Ranch Hand

Joined: Apr 21, 2006
Posts: 1847
For booking I send the entire record, and write the entire record.
Much easier that way to expand the application in the future to modify other records as well (and keeps the database engine flexible, rather than being fixed to update a single column only).

The update method returns no records (at least in my version of the assignments). Instead after an update (whether failed or successful) I refresh the currently loaded recordset from the database by applying the last search criteria again.
This will get the updated record from the database, as well as any others updated elsewhere.

The Data class to me isn't a singleton.

I agree. Here's the link:
subject: B&S Design Decision
It's not a secret anymore!