This week's book giveaway is in the OCAJP 8 forum. We're giving away four copies of OCA Java SE 8 Programmer I Study Guide and have Edward Finegan & Robert Liguori on-line! See this thread for details.
After reading a lot of topics here on JavaRanch I still have on question which is kind of bothering me... Do we really need a GUI for the server part of the assignment?
I'm using RMI and I've 'semi' hardcoded the port number the server uses. With this I mean that the server port used is set in the suncertify.properties file (standard 1109), but there is no interface to change this. I figured that since this is the standard RMI port why not use it? I've also hardcoded that the database file should be located in the user.dir.
As far as I've been able to tell there is no requirement that states that you should provide a GUI for the server, but maybe I've missed it and it's hiding between the lines... Could somebody shed some light on this for me?
Do your instructions have the following line (or something similar) in them: If so - are you assuming that this only applies to the client application?
Yes the assigment does have a line like that. That was one of the things that started me thinking about my whole server approach. But on the other hand, I'm convinced that a server should not have to be used through a graphical user interface. A server (in my opinion) is a daemon process that runs in the background.
I have been working on the assignment yesterday and I've written a small GUI for the server which lets the server itself keep running when the GUI is closed (but there is a button to 'savely' stop the server).
As you have to carefully consider each 'must' case, I suggest you read your assignment again and find out are there any 'must' for GUI specification. If there's not, then you may but you don't need to use GUI for server.
My suggestion is, if you won't get more error using GUI, then you'd better use it, as it's easy for user to control and easy to trace exceptions.