What you're expected to demonstrate is code that does and does not require a network connection. This means one section of your code will not be able to use RMI.
This raises an interesting issue -- how to write server code that can protect shared data regardless of the type of connection the client has. In short, you have to separate issues of thread and synchronization from connectivity. Not hard, really, but you do have to think it through.
Michael Ernest, co-author of: The Complete Java 2 Certification Study Guide
I passed the SCJD sometime ago with a good score but I dropped 20% on my GUI which I had thought was really great. The thought has just occured to me that maybe I mis-interpreted the requirements. I always planned to implement my direct access connectivity on my server until I really gave it some thought after which it really seemed pointless. I then implemented direct access on the client using a separate database which worked fine and seemed to satisfy the requirements. Do you feel that the Client in Direct Access mode should connect to an existing Database running on the same machine and therefore in the same VM?
My original plan was to have my simple server GUI with a button that launched a non-networked version of the client.
I don't need an answer, I'm just curious.
Originally posted by Michael Ernest:
Be careful how you think about direct access! The question here is ensuring that synchronization takes places regardless of the type of connection. If your scheme for "direct access" doesn't conflict with that, you're good to go.