Your data access class must be called Data.java, must be in a package suncertify.db and must implement the DBAccess interface
//Locks a record so that it can only be updated or deleted by this client.
// Returned value is a cookie that must be used when the record is unlocked,
// updated, or deleted. If the specified record is already locked by a different
// client, the current thread gives up the CPU and consumes no CPU cycles until
// the record is unlocked.
I am planning to architect the system with the following components
3. Database Layer
Now in network mode the GUI access's the server via the RMI Interface. In Non gui mode the GUI access's the servers code directly, bypassing the RMI interface altogether ( as per the spec )
Now in the spec SUN mention the following:
quote: The mode is selected using the single command line argument that is permitted. Architecturally , this mode must use the database and GUI from the networked form, but must not use the network server code at all.
Does this mean in non-networked mode my GUI has to access my Database layer directly and not access the server code at all. Or does it mean I must not use the Server RMI interface, but I'm ok to access the actual Server methods??
The mode is selected using the single command line argument that is permitted. Architecturally , this mode must use the database and GUI from the networked form, but must not use the network server code at all.
Just to clarify, I see the collection of configuration data as a seperate step prior to running the application so no matter what mode I use, a dialog pops up asking for the relevant config data for that mode. If a suncertify.properties file exists, the fields are filled in with the data from the file.