Thanks for the info.
There seem to have been many suggestions to improve the initialization
and even some patches (like
http://www.mail-archive.com/turbine-jcs-dev@jakarta.apache.org/msg00369.html
).
Any reason why these suggestions were rejected? They seem to be better
than what is currently implemented - IMHO!
Tim Cronin wrote:
You don't have to put it in the classpath you can do the following
CompositeCacheManager ccm =
CompositeCacheManager.getUnconfiguredInstance();
Properties props = new Properties();
props.load(/* load properties from some location defined by your app
*/);
ccm.configure(props);
-----Original Message-----
From: Alistair Forbes [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 13, 2005 4:25 PM
To: jcs-users@jakarta.apache.org
Subject: Config file placement
Is it possible to specify the path to the config file?
Something like: -Djcs.configfile=../config/cache.ccf
This would be preferrable to using the classpath.
A null-check on the current setup would probably also help some folks.
diff -u -r1.14 CompositeCacheManager.java
--- src/java/org/apache/jcs/engine/control/CompositeCacheManager.java
4 Jun 2005 02:01:58 -0000 1.14
+++ src/java/org/apache/jcs/engine/control/CompositeCacheManager.java
13 Dec 2005 22:13:48 -0000
@@ -162,6 +162,12 @@
Properties props = new Properties();
InputStream is = getClass().getResourceAsStream( propFile );
+ if (is == null)
+ {
+ logger.error("Failed to load " + propFile
+ + "Try /" + propFile + " if in the root
classpath.");
+ }
+
Regards
Al
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
