I have a question about the configuration application. Sun requirements says that the assessor shouldn't hand edit any file. So I came up with a GUI base application which enables user to update configuration information. I've added this as an extra command line parameter. So I have
[alone | server | config].
And absence of any parameter runs the application GUI in networked mode.
Do you think that might be a problem. Cause according to requirements, he should only have
[alone | server] command line parameter?
I think you are not meeting this requirement, which is a must requirement meaning you can get automatic failure.
From the instructions:
Your programs must not require use of command line arguments other than the single mode flag, which must be supported.
In my opinion it is better to bring up the configuration GUI every time (with default values loaded), which the assessor can just confirm or change as required.
Sounds good. The only additional thing I would do is make sure that the database that was selected the last time the application was run (if any) is offered as a default this time around. This is to meet with the following requirement:
From the instructions
All configuration must be done via a GUI, and must be persistent between runs of the program. Such configuration information must be stored in a file called suncertify.properties which must be located in the current working directory.