Exam Number: CX-310-252A
Associated Certifications: Sun Certified Java Developer (SCJD)
Assignment Price: TBD
Assignment Registration: This item is currently unavailable while we update the process. If you previously purchased this assignment, the files will be sent to you via email.
Duration: 12 months from assignment download
Number of Questions: NA
Passing Score: 320 points out of 400 possible points*
* Passing score is subject to the evaluation of the Step 2 essay exam and validation of the authenticity of the assignment
Roel De Nijs wrote:Jason,
How big is your delete flag according to your instructions? What's the declaration for your Room.VALID_RECORD ?
 I guess your delete flag is 2 bytes, so you would use writeShort and readUnsignedShort for the reading/writing of your deleted flag. More info about this in this thread.
Roel De Nijs wrote:Hi Jason,
I guess it all depends on how big the delete flag is. In my assignment the flag was 1 byte.
So i was able to successfully write my delete flag with the following code:
K. Tsang wrote:Hi Jason,
For your questions, ideally you just need to enter the customer ID (owner field) which is 8-digit string, not the customer name like you said. All other fields don't need to change, but if you want you can change the date to the check-in date (ie 2 days from today satisfying that 48 hour rule).
Don't worry if you worked on the assignment more than one year, I think the one-year period applies to new candidates.
Also when you do submit, you need to submit the original database file that came with your assignment (no new records, no deleted records, no changed fields).
Roel De Nijs wrote:Hi Jason,
I have implemented all methods from DBAccess (and even some own methods I needed) in my Data class: so I have in my Data class a create- (reusing deleted entries), update-, delete-, read-, find-, isLocked-, lock- and unlock-method.
I only used these methods in my program: find (look for rooms), read (read the rooms), update + isLocked + lock + unlock (book a room). So create- and delete-method are unused.
If you want to test your methods (see if implementation is ok and they act like they should) I would create a test-case (or test-program, something like Junit, TestNG). I even suggest this for all your methods, certainly for your Data class (it's the most important class you will create). I created a Data class test with 100% coverage (so each situation is tested, also those when you pass a wrong/illegal parameter). I have a 68 different tests (for just 11 methods ). The benefit of this approach: if you make some changes after a week to your Data class, you just run your test-case and you see immediately of those changes broke your existing code. And of course running just this test-case is a lot easier and faster than starting whole your application to see if an update was successful
But you don't have to use all methods from Data. I created a second find-method (returning record numbers + record data instead of just record numbers). And in my program I use that one instead of the one defined in Sun's interface.
 don't forget to make a backup of your original database file (if you start updating, deleting,...) because you have to submit an original (unchanged) database file)
K. Tsang wrote:
Jason Marshall wrote:How do I open a new JPanel that exists within the same JFrame?
Hi Jason, how are you doing book or search? Are you using internal frame (like you are currently) or popup frame/dialog?
The idea should be the same. Creating or delete records is the least worry of the GUI. Searching and booking (updating) are the key requirements you must implement.