You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2007/02/13 13:05:05 UTC

[jira] Closed: (COCOON-1927) ehcache files in java.io.tmpdir

     [ https://issues.apache.org/jira/browse/COCOON-1927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler closed COCOON-1927.
------------------------------------

       Resolution: Fixed
    Fix Version/s: 2.2-dev (Current SVN)
                   2.1.11-dev (Current SVN)

> ehcache files in java.io.tmpdir
> -------------------------------
>
>                 Key: COCOON-1927
>                 URL: https://issues.apache.org/jira/browse/COCOON-1927
>             Project: Cocoon
>          Issue Type: Bug
>          Components: * Cocoon Core
>    Affects Versions: 2.1.10
>            Reporter: Richard Frovarp
>            Priority: Minor
>             Fix For: 2.1.11-dev (Current SVN), 2.2-dev (Current SVN)
>
>
> Running the demo Cocoon Jetty servlet results in the ehcache files being put into java.io.tmpdir instead of Jetty__xx___/cocoon-files/cache-dir. This change seemed to take place with the change to ehcache 1.2. Looking through the ehcache documentation, the constructor has changed, and if the old constructor is used, it will put the cache files in java.io.tmpdir, instead of the location specified. This also affects other projects using Cocoon, resulting in being able to run only one instance, without changing the java.io.tmpdir directory for each instance.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.