aspose file tools*
The moose likes Developer Certification (SCJD/OCMJD) and the fly likes Anyone passed SCJD without putting wait on locked record? 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 "Anyone passed SCJD without putting wait on locked record?" Watch "Anyone passed SCJD without putting wait on locked record?" New topic
Author

Anyone passed SCJD without putting wait on locked record?

Bram Pramono
Greenhorn

Joined: Feb 19, 2009
Posts: 6
Hi guys,

This is a thing I'm very curious about. I just had a discussion with Roel and K.Tsang (link) about should threads trying to lock a locked record wait? or get an error message mentioning that a record is lock, please try again later? I feel that with my assignment and solution, error message seems to be good, but Roel and K say otherwise.

So please for people who did passed SCJD without using wait on lock, let me know. Thank you.

Cheers,

Bram


SCJP 5
Fernando Franzini
Ranch Hand

Joined: Jan 09, 2009
Posts: 486
    
    2

Hi Bram

I dont think that there are anyone in this situation cause lock/wait are mandatory requirements ! If you dont implement, you'll have automatic faill.
Look my assignment:

Where this document uses the word "must" an absolute requirement is being described. If you fail to adhere to such a requirement, your assignment will be failed automatically, and without further evaluation. It is therefore imperative that you pay close attention to any statement using the word "must" in this document. Portions of your submission will be analyzed by software; where a specific spelling or structure is required, even a slight deviation could result in automatic failure.


Locking
Your server must be capable of handling multiple concurrent requests, and as part of this capability, must provide locking functionality as specified in the interface provided above. You may assume that at any moment, at most one program is accessing the database file; therefore your locking system only needs to be concerned with multiple concurrent clients of your server. Any attempt to lock a resource that is already locked should cause the current thread to give up the CPU, consuming no CPU cycles until the desired resource becomes available.

So..if your assignment dont tell you this....you can let this implementation out.
Regards.


Fernando Franzini - Java Blog
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Anyone passed SCJD without putting wait on locked record?