Hi,
I put System.setProperty(java.awt.headless, true);
in my servlet init method it's ok, but now when I open a Frame,
I get the exception HeadlessException:
java.awt.HeadlessException
at
java.awt.GraphicsEnvironnement.checkHeadless(GraphicsEnvironement.java:121)
at
ok: there is another solution to the headless thing: (I wrote a
graphical servlet that runs on a linux box without X, and had the same
problems: The headless seemed to work, well, kinda, but not to my
liking): So I went the xvfb route: This is a virtual frame buffer to can
install on a linux box
Difficult to say: What kind of problems?
I start mine using
Xvfb :0 -screen 0 1600x1200x32
{I just added it to rc.local }
On Thu, 2003-03-20 at 19:27, Glenn Parsons wrote:
At 07:18 PM 3/20/2003 +, you wrote:
ok: there is another solution to the headless thing: (I wrote a
graphical
Hi,
Another common (Java) solution is to install PJA Toolkit:
PJA (Pure Java AWT) Toolkit is a JavaTM library for drawing graphics
developed by eTeks. It is 100% Pure Java and doesn't use any native graphics
resource of the system on which the Java Virtual Machine runs.
java.awt.Graphics methods
Yep: Done correctly, this is probably the more 'correct' solution, but,
and I'm probably opening myself to a lot of flamebait, but I do suspect
that using something like Xvfb might give some advantages that using
headless won't. For example, and I'm just guessing, but I think that
'headless' is
Hi,
I would say that Xvfb does _not_ connect to your display adapter - the v
stands for virtual, ie it's not a real frame buffer as in a video card -
it's a virtual one in your systems normal memory.
It's specifically for taking the place of a display adapter when your server
doesn't have one.
