search

alexo / wro4j

New project location is:https://github.com/wro4j/wro4j
442 stars 110 forks source link

disableCache=true not working in debug mode ? #192

Open sebdavid opened 10 years ago

sebdavid commented 10 years ago

Hi, I'm using wro4j 1.7.6 at runtime. It seems that using the property disableCache=true has no effect, whereas it was working with 1.7.5. Here is my wro.properties :

cacheUpdatePeriod=0
modelUpdatePeriod=0
debug=true
disableCache=true
gzipResources=true
ignoreMissingResources=false
jmxEnabled=true
preProcessors=cssUrlRewriting,cssImport

Running with log4j set at DEBUG, during the first access, I can see wro4j working in getting all the files, etc. All next accesses are just displaying the following lines :

2014-08-25 09:34:29,249 DEBUG processing wro request: /mycontext/resources/wro/libraries.js
2014-08-25 09:34:29,249 DEBUG period: 0 [SECONDS]
2014-08-25 09:34:29,249 DEBUG period: 0 [SECONDS]
2014-08-25 09:34:29,250 DEBUG Searching cache key: ro.isdc.wro.cache.CacheKey@187b6ba[type=JS,groupName=libraries,minimize=true,map={}]
2014-08-25 09:34:29,250 DEBUG shouldWatchForChange=false
2014-08-25 09:34:29,250 DEBUG Gzipping the content....

The problem is that the server has to be restarted after each resource modification. A workaround is to set the properties cacheUpdatePeriod and modelUpdatePeriod to another value than 0, to refresh the cache. Thanks in advance for your answer, Sébastien.

alexo commented 10 years ago

Hi,

It was removed on purpose, since it was causing a bug and also there is an alternative to replace it. For more details search the issue 871 on google code page. Let me know if you have any questions.

I will close this issue, since it is an expected behavior.

sebdavid commented 10 years ago

Ok. As I didn't find a related issue in the content of the milestone 1.7.6, I thought it was an issue. Here is the link from the google code issue for interested people : http://code.google.com/p/wro4j/issues/detail?id=871 Edit : the documentation should be updated if the "disableCache" property doesn't exist anymore.

alexo commented 10 years ago

The release notes and complete details are still hosted on google code page, there wasn't yet a complete migration to github. I must admit that this might be confusing, but it will hopefully be improved at some point.

Thanks, Alex