DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7200>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7200 loading config.xml [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |FIXED ------- Additional Comments From [EMAIL PROTECTED] 2002-06-06 19:21 ------- The userconfig appears to be ok. Some more digging revealed that the given version 0.17 does not have the Option class. The 0.18 release had an exit() in the loadStandardConfiguration() method in case the configuration file is not found (means: missing or not accessible from the jar file. An error message should have been logged in this case. It is possible that WebSphere has problems accessing ressources in the fop.jar file, perhaps intetional because of dynamic class loading. It is strongly recommended to upgrade to 0.20.3 which does some classloader magic in order to avoid such problems. FOP 0.20.3 is known to work on various configurations of Websphere 3.5 and 4.x. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
