Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Date: 27 Feb 2004 13:52:59 -0000
Message-ID: <20040227135259.20222.qmail@nagoya.betaversion.org>
From: bugzilla@apache.org
To: dev@cocoon.apache.org
Cc: 
Subject: DO NOT REPLY [Bug 27249]  -
    You cannot lookup components on a disposed ComponentLocator exception

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=27249>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=27249

You cannot lookup components on a disposed ComponentLocator exception


------- Additional Comments From bdelacretaz@codeconsult.ch  2004-02-27 13:52 -------
> So this seems to be solely related to the parsing of the XML
> comment containing the CVS version info.

hmm..if you remove the $Id$ keyword, CVS won't do any change to the file when
doing the commit, so the problem is not necessarily related to the comments.

I was more thinking of the way used by CVS to update the file (some sequence of
file open / write / close / file date change) which causes Cocoon's "file change
detection" to do something funny. 

It might be interesting to look at the debug messages related to how the
sitemap.xmap change is detected by Cocoon.