RE: FOP and WebObjects yet again.
RE: FOP and WebObjects yet again.
- Subject: RE: FOP and WebObjects yet again.
- From: email@hidden
- Date: Fri, 7 Apr 2006 13:41:26 +1200
Hello Zac;
When instances of the driver have to have an instance of the
org.apache.avalon.framework.logger.* set. By default (ie if you
don't set the logger) the Driver object uses avalons' ConsoleLogger.
I had some trying "log4j" and "jakarta commons logging" problems and
conflicts some months ago and to beneficially work around the
problem, I wrote my own "commons logger" to funnel the log lines back
into WO's logging system -- avoiding log4j. See the class
"LEWOCommonsLoggingLogger" in my LEWOStuff framework (you can
download this from my home page) and then read the section "Jakarta
Commons Logging" in the overview PDF.
Here is what I think is happening. When I run the app on my local
machine I own the process and have access to the window server so
everything is fine.
There is a command-line argument you can pass into the JVM...
-Djava.awt.headless=true
This will make the graphics environment of the JVM work without
needing the window server. If you're not already doing this, give it
a go and see if it resolves your issues.
All the best.
cheers.
___
Andrew Lindesay
www.lindesay.co.nz
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden