Title: RE: Problem with cache?

> From: Sergio Garc�a [mailto:[EMAIL PROTECTED]]
>
> First of all, make a directory in G like this
>      
>     md temp/JeetspeedDocumentCache
>
> and put in the config file this :
>
>     cache.directory=/temp/JetspeedDocumentCache

This doesn't seem to help. I DO have a directory (under D:)
called /tmp/JetspeedDocumentCache, and my JetspeedResources
properties file points to it. The relevant contents are:

  cache.directory=/D:/tmp/JetspeedDocumentCache
  public.cache.directory=/D:/tmp/jetspeed-cache
  temp.directory=/D:/tmp

All three directories exist. After cleaning them up, running
Jetspeed and hitting the page, these are the contents on
each directory:

D:\tmp\JetspeedDocumentCache:
http.banco109..sonda..cl...80.content.dynamic.index..xml                180 bytes
http.banco109..sonda..cl...80.content.dynamic.index..xsl                217 bytes
http.banco109..sonda..cl...80.content.static.search..html              5511 bytes
http.banco109..sonda..cl...80.content.xml.defaultPortlets..xml         2513 bytes
http.banco109..sonda..cl...80.content.xml.rss.Jetspeed..rss            1072 bytes


D:\tmp\jetspeed-cache:
http.banco109..sonda..cl...80.content.images.jetspeed-powered..gif     4304 bytes

So, the files have what (to me) look like extra dots. The thing
is, the log file seems to prove that Jetspeed is expecting even
more dots (lines wrapped for legibility):

> [Thu Jul 20 17:59:58 GMT-04:00 2000] --  ERROR  --
> CocoonPortlet: Could not use the following URL:
> http://banco109.sonda.cl:80/content/dynamic/index.xml
> <http://banco109.sonda.cl:80/content/dynamic/index.xml>
> /D:/tmp/JetspeedDocumentCache\file..D....tmp.
> JetspeedDocumentCache\http..banco109....sonda....cl......80..
> content..dynamic..index....xml
> (The system cannot find the path specified)

Any other hints? I have tried changing the properties file to use
several combinations of /D:/tmp/..., /tmp/..., tmp/..., etc.,
to no avail. Thanks,


--
Gonzalo A. Diethelm
[EMAIL PROTECTED]
If this mail is in HTML format, blame Exchange Server: Q222508

Reply via email to