Something keeps on truncating my FOP configuration file - fop.xconf in the conf directory. The file still exists but has 0 bytes. This has happened several times.
Does FOP open its configuration file read-write? Could a premature abort of FOP cause the fop.xconf file to be truncated? Best Regards, Jonathan Levinson
