Subject: RE: Changing java system property - Headless java - PJA
Certainly Joseph. It’s all turned out to be a red herring slightly, albeit an interesting one. I’ve now found a way to do this with JIMI, as suggested by the guy who wrote PJA.
If you go back to
http://www-10.lotus.com/ldd/nd6forum.nsf/DateAllThreadedweb/0695a012497f660f85256e2e004515fb?OpenDocument
What I’m doing is this. Users choose a JPEG from their own file system, I force the user to rename it to something sensible, post/save it, extract it to the Linux file system, pick it up, create a thumbnail, create a full size image of the desired size, post back to the user to show them the results. All was fine in Windows then I tranferred dev to Linux.
You’ll see where the discussion began but the long story short is that the Linux box is running headless, no X so no libraries that the JVM needs for processing 2D graphics are available. Domino /is/ running in a console, no X is loaded.
So, I did fiddle with PJA for a bit, you modify the java.policy file to allow awt.toolkit to be read/write and then set the property to point at the eteks PJA solution, which doesn’t use the overlying system’s graphics, it renders graphics ‘pure’ using native java and Brasenham algorithms. Well, you would, wouldn’t you 
Also modified the notes.ini to include the pja.jar file and made the output verbose so I could see what’s going on. I can see that PJA is being used in the verbose output. There comes a point in the code where you call createGraphics(), and this is where is crashes.
It’s totally reproducible but the JIMI way is vastly superior. All you need is the X11 libraries to be loaded on the server, no X is needed to run and no modifications are required to the java.policy file or notes.ini. I merely added JIMI.zip or whatever it’s called to the project for the agent in use.