Details
-
Bug
-
Status: Resolved
-
Resolution: Duplicate
-
1.7
-
None
-
None
-
Operating System: Linux
Platform: All
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.
Attachments
Attachments
Issue Links
- duplicates
-
BATIK-740 [PATCH] Headless problem in transcoders
- Resolved