Richard Frovarp wrote:
Here is what I've found. If I download Cocoon 2.1.9 and run it as a
test
application, it will dump the cache files in
Jetty__8888__/cocoon-files/cache-dir. If I grab the latest snapshot,
that directory exists, but the cache files are not in that directory.
Since that directory obviously has the port in its name, running
multiple copies in the past would not have been an issue. Now the
files
follow the java.io.tmpdir property. If you change this property,
you can
get it to put the cache files in different locations.
The ehcache can be configured in a file called ehcache.xml. You can find
this file in your cocoon dir e.g.
./cocoon-2.1.X/src/java/org/apache/cocoon/components/store/impl/ehcache.xml
Within this file you can (among other things) set the diskStore path
(defaul is: <diskStore path="java.io.tmpdir"/>).
BTW, i would recommend to change the entries for productive use anyway.
the <defaultCache> too. By default eternal is set to true which lead
to quite big cache files for our installation.
HTH
Jann
I have looked at that file. Both the 2.1.9 and snapshot have the same
contents, which is the default you list. Why is one putting the cache
into the Jetty cocoon directory and the other into /tmp. I suppose
this is a question for the cocoon group.
Richard
I found the issue. They switched from ehcache 1.1 to 1.2 and the
constructor changed. I have filed a bug with the Cocoon group.
Richard
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
