cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carsten Ziegeler" <cziege...@sundn.de>
Subject [C2]: Strange component management behaviou
Date Tue, 26 Jun 2001 09:34:52 GMT
Hello,

after some testing, the strange behaviour reported by Giacomo a few days ago
is
reproducable here:
Installing a clean, uptodate C2 into Tomcat 3.2.1, JDk1.3, Windows 2000 is
working first fine: When I call cocoon/welcome it is served with the
CachingEventPipeline.

However changing the modification date of the cocoon.xconf file without
modifying anything creates a new cocoon object, BUT from now on the
NonCachingEventPipeline is used!
When restarting cocoon with deleting the work directory first produces
the correct behaviour: The CachingEventPipeline is used.
Then again changing the modification date and voila the
NonCachingEventPipeline is happy to serve the request.

Attached is the log of the first run. Does anyone have a clue for this?


Carsten

Open Source Group                        sunShine - b:Integrated
================================================================
Carsten Ziegeler, S&N AG, Klingenderstrasse 5, D-33100 Paderborn
www.sundn.de                          mailto: cziegeler@sundn.de
================================================================

Mime
View raw message