|
From: Walt Teh-M. Y. <wal...@as...> - 2003-09-16 09:18:55
|
Hi, I'm trying to get Babeldoc 1.1.9-dev to work in a J2EE web project. However it doesn't seem to pick up custom configuration files that I put under WEB-INF/classes. I successfully integrated the stable version (1.0.2) to the project by supplying configuration files in the classpath under WEB-INF/classes and it does pick up and initialises itself properly. After looking into the source, it seems like getN_MatchingUrlsInSearchPath() in com.babeldoc.core.ResourceLoader always adds the classpath to the end of the search path. If I understand the source correctly, this means the configuration files in the classpath are considered the *most general* and will be overridden subsequently if the same configuration options are found in the jar files. And as the core jar includes a set of default configuration files, it seems impossible to override those defaults by supplying configuration files at the classpath. I wonder if someone could explain why the classpath is added after all modules search paths. Ps/ I'm aware that by setting the system property babeldoc.user, I'll be able to override the default configuration. But I'd like to be able to do it from the classpath where possible. -- Walt |