(1) Did you simulate current clients for load testing the RMI Application?
No, I used some of the people in my office for testing. I also added some sleep commands in the method making the bookings to make sure the would be attempting to access the same database record at the same time.
(2) How you implemented the online help?
I created a html file and included it in my client jar file. I used a JEditorPane to display the html file in. I didn't have to hard code any paths because the file is guaranted to be in the jar file.
(3) Will be lock be blocked for new requests, when the client that locked the records crashes without unlocking the record?
If the client crashes and it holds a lock that record will remained locked until the server is restarted. They didn't say it had to be production level just functional.
(4) And, Can you give us few tips on writing the readme, desing and other documents.
The readme file is pretty simple. It was a bit long just because I gave detailed instructions on running the program and listing each file submitted with a description. I had a total of nine points I disucssed in my design doc including RMI, Locking Scheme, Modyfing Data, Exception Handling, GUI Design, Event Handling and a couple of other small things.