FOP [1] uses Avalon Framework's DefaultConfigurationBuilder [2] to load config files. This in turn uses the system's default SAXParserFactory. I don't think any of that code would overwrite the config file. Either this is overwritten by a build process somewhere or by your code. After all, there are various ways how the configuration can be loaded. At least I've never had the problem that my FOP config files were killed.
[1] http://svn.apache.org/viewvc/xmlgraphics/fop/trunk/src/java/org/apache/fop/apps/FopFactoryConfigurator.java?view=markup [2] http://svn.apache.org/viewvc/excalibur/trunk/framework/impl/src/main/java/org/apache/avalon/framework/configuration/DefaultConfigurationBuilder.java?view=markup On 15.02.2010 23:09:12 Jonathan Levinson wrote: > 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 > Jeremias Maerki --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
