This week's book giveaway is in the Agile and other Processes forum. We're giving away four copies of The Mikado Method and have Ola Ellnestam and Daniel Brolund on-line! See this thread for details.
Hi all, just I got my result. Of course I'm happy to have passed but the score is disappointingly low, especially the GUI section. Furthermore I waited for my result since March 29. Here are images of my GUIs. Can someone explain me what is wrong with them?
Thanks to all here. Werner
Hanna Habashy
Ranch Hand
Joined: Aug 20, 2003
Posts: 532
posted
0
Congratulation Werner Your score is not bad, I wish I just can pass with the same score
SCJD 1.4<br />SCJP 1.4<br />-----------------------------------<br />"With regard to excellence, it is not enough to know, but we must try to have and use it.<br />" Aristotle
Baris Dere
Ranch Hand
Joined: Mar 23, 2004
Posts: 31
posted
0
Congratulation Werner, A good score. When I saw your client GUI, I couldn't see your book button. When I looked becarfully I saw it. Maybe due something like this. So now hope I can pass ;-) Success with your next examen. Baris Dere
Baris Dere
Ranch Hand
Joined: Mar 23, 2004
Posts: 31
posted
0
Werner, How did you implement locking mechanism? Can you tell us a bit about it? Thanks Baris Dere
Werner Joerling
Ranch Hand
Joined: Mar 23, 2003
Posts: 35
posted
0
Originally posted by Baris Dere:
How did you implement locking mechanism?
I did the locking mechanism similar to that in Mehran Habibi's book. There isn't a lock manager, but rather a
intended to store the locked records. All record access methods (read, find, create, delete, update) in the Data class are synchronized by the method modifier 'synchronized'. ('create' and 'delete' aren't really implemented, they simply throw UnsupportedOperationException). The lock methods (lock, unlock, isLocked) are using synchronized blocks
and the 'unlock' mehod calls
when recNo has been removed. The single record access methods (read, update, delete) throw IllegalStateException if the recNo isn't locked. The bulk record access method 'find' uses lock/read/unlock inside a loop over all records and skips deleted records. There is a middle tier (locally or remotely accessible) between the clients and the DBMain interface that implements the high level methods 'book' and 'search' and ensures the correct use of the lock/unlock protocol (db is of type DBMain).
Werner [ May 12, 2004: Message edited by: Werner Joerling ]
Andrew Monkhouse
author and jackaroo
Marshal Commander
Congratulations Werner Your GUIs looked fine to me - there are some things I would do differently, but nothing major. Since you are using the platform L&F there may have been something odd happen when run on a different platform (unlikely, but possible). Does your screen resize nicely? Regards, Andrew
Originally posted by Werner Joerling: All record access methods (read, find, create, delete, update) in the Data class are synchronized by the method modifier 'synchronized'. ('create' and 'delete' aren't really implemented, they simply throw UnsupportedOperationException).
Empty create()/delete() methods are a bit tempting! [ May 13, 2004: Message edited by: Vishwa Kumba ]
Andrew Monkhouse
author and jackaroo
Marshal Commander