[BATIK-913] Avoid java.awt.HeadlessException when using WMF transcoder functionality

• Type: Bug
• Status: Resolved
• Resolution: Duplicate
• Affects Version/s: 1.7
• Component/s: (RFE) Request For Extension
• Environment: Operating System: Linux; Platform: All
• Assignee: Batik Developer's Mailing list
• Reporter: Gabriel Gajdos
• Created: 28/May/09 01:43
• Updated: 29/Nov/09 03:27
• Resolved: 29/Nov/09 03:31

Description

I was using Batik with Jasper with some WMF images.

Everything was working perfectly in my Windows GUI environmenet.
But after deploying to server without available display GUI I got java.awt.HeadlessException.
Setting -Djava.awt.headless=true was not sufficient.

I started small investigation and I identified the problem:
Toolkit.getDefaultToolkit().getScreenResolution().

I modified two classes (attached AbstractWMFReader and AbstractWMFPainter) which use this call with a simple workaround.
1. only one call to this method is needed (subsequent calls can use final static variable already declared).
2. If a HeadlessException is thrown, we assume (hardcoded) resolution 96 (current value from my GUI environment).
I think it is better to have this hardcoded output than thrown exception.

I tested this new classes and result was OK without thrown Exception.

I past my minor changes fot the case that someone else would appreciate server-side functionality for reading WMF files.

Issue Links

• duplicates: BATIK-740 [PATCH] Headless problem in transcoders