rmiregistry should be started programmatically
A user wanting to use the distributed system should not have to start the rmiregistry manually. kepler should start this for him/her when it starts up.
Updated by jianwu jianwu over 13 years ago
Users may start Kepler GUI at slave side. They also may only need to start slaveController especially when they can only access slave remotely.
So rmiregistery should be started either by starting Kepler GUI or a separate slave controller start command line (similar to previous ant runSlaveController).