This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
I've got my project (codewise) finished (URLyBird 1.3.2), just tidying up the javadoc and fixing a few small PMD issues.
I've been reading how people have been running the server on another machine and connecting remotely from another machine.
My question is "Is this required?"
The requirements state for RMI
To avoid unnecessary complexity in the marking environment certain restrictions are placed on solutions that use RMI. Specifically:
You must not require the use of an HTTP server. You must not require the installation of a security manager.
You must provide all classes pre-installed so that no dynamic class downloading occurs.
You must use RMI over JRMP (do not use IIOP)
Well champion, yes... since it is a server. The idea is that you can start an RMI application that listens to requests on a specific port, and connect to this server in this specific port. This means that you cannot use an HTTP server, such as Tomcat, Glassfish, JBoss, etc. That's pretty much it.
I must explain my reasons for asking the question.
I was testing it across my personal laptop and my work laptop but it wouldn't work (My work laptop has a ridiculous amount of security on it).
One of my mates called over with his personal laptop an hour ago and we tried it and it works perfectly!
Going to submit it this weekend!
Well champion, if you tried to have your client connect to your server over a network, didn't use an HTTP server and didn't use IIOP, then I'd say you're good to go! My wishes of good luck to you, champion!
I don't remember exactly, but there is some mention in the requirement that the test machines won't be having extra security (or something like that).
In my case, I worked on a Linux distro, and while testing, I disabled SELinux module (Security Enhanced Linux). I didn't even tested it with SELinux.
However, in choices.txt (or the file where you mention OS and Java details), I specifically mentioned that this code has been tested on <Linux distro name and version>, <Java version> with SELinux disabled.
I didn't face any issue during the exam.
Also, I think Andrew Monkhouse's book discusses this issue (i.e. sometimes, RMI fails when MS Windows firewall is active).
I'm not sure on which OS you are testing, but as your testing is successful, please mention the configuration in your documentation (i.e. which OS was used for testing, what were the security settings and so on) and you should be good.