Jini configuration hell

Since its introduction, pundits have wondered why Jini has failed to catch on like other Java technologies. Having recently tried to take the plunge into JavaSpaces, I believe I can answer that question.

Put simply, Jini is too hard to configure. I consider myself fairly intelligent, and I have a lot of Java experience and a fair amount of Solaris experience. Nevertheless, it took me over a week of wasted evenings trying to run the Ray Tracer example included with the Jini distribution. Running this example requires no less than 6 processes to be running, 4 of which require commands spanning multiple lines to start.

You can see the fruits of my labor, a shell script that starts everything running. For everyday use, I’ve broken it into 5 different shell scripts: jini-start-all.sh, jini-start.sh, jini-stop-all.sh, jini-stop.sh, and one for the application (e.g., browser.sh or raytrace.sh).

I haven’t even started writing my own programs, this is just to run the example. Folks, developers are going to be slow to adopt Jini until this get easier.

Comments are closed.