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 [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Version|Current CVS 2.0 |Current CVS 2.1 ------- Additional Comments From [EMAIL PROTECTED] 2004-02-28 13:20 ------- > 1 Did you really mean to change to current _2.0_ for this bug? Sorry no, fixed it > 2 Are you using eclipse (for cvs commit)? No, command-line CVS. But I haven't been able to reproduce the problem with simple sitemaps, for now I only see it in my application. In the meantime I have added log messages to the CocoonComponentManager, which show the problem: IIUC the sitemap component manager is disposed, and later on AbstractEnvironment calls lookup() on this disposed manager, causing the ExcaliburComponentManager to complain. The attached logs show the problem, search for "CocoonComponentManager.dispose" in sitemap.log (next attachment "log with additional CCM messages") I don't know enough about CocoonComponentManager to go further - either it is disposed at the wrong time, or its sourceResolver should not be set to null in dispose(). The relation to the CVS commit is still a mystery though, but the above failure scenario with CVS works every time here ;-)
