Perhaps JCS should try to load the config file from the filesystem, and if that fails then from the classpath if the former is not found?
(More consistent at least) On Wed, 2002-05-29 at 14:23, xMySign for JCS wrote: > I got the solution, I just didn't put the cache.ccf > in the right directory! but why this has to situate > in the WEB-INF/classes? I think it's because JCS loads > the property file with getClass().getResourceAsStream () and this > method tries to load in the same path as the class file > of the current Class resides. But is this common? Velocity > detects the path to the file with File(file).getAbsolutePath(). > so if the configuration files are in the directory webapps/myapp/WEB-INF/conf > for JCS I have to configure > JCS.setConfigFilename( "/../conf/cache.ccf" ); > and for Velocity (and some other projects like Log4J) I have to set > the path to "/WEB-INF/conf/xxx.properties". Wouln'd it be a > good idea if the root in all projects would be the same, or > what's the reason to use in one case getResourceAsStream and > in the other getAbsolutePath? > > mike > > > Please send the cache.ccf that you are using. > > > > You probably need to put in the default configuration lines. > > > > There is some documentation on the JCS web site that may help. > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
