Return-Path: 
 <cocoon-dev-return-39374-apmail-xml-cocoon-dev-archive=xml.apache.org@xml.apache.org>
Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org
Received: (qmail 37418 invoked by uid 500); 28 Mar 2003 09:55:31 -0000
Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:cocoon-dev-help@xml.apache.org>
list-unsubscribe: <mailto:cocoon-dev-unsubscribe@xml.apache.org>
list-post: <mailto:cocoon-dev@xml.apache.org>
Reply-To: cocoon-dev@xml.apache.org
Delivered-To: mailing list cocoon-dev@xml.apache.org
Received: (qmail 37405 invoked from network); 28 Mar 2003 09:55:31 -0000
Received: from node1a14f.a2000.nl (HELO naomi.webworks.nl) (24.132.161.79)
  by daedalus.apache.org with SMTP; 28 Mar 2003 09:55:31 -0000
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
Subject: RE: disposed ComponentLocator
Date: Fri, 28 Mar 2003 10:56:30 +0100
Message-ID: <84F0A43A4248CE45B5C0E20F4C40779C6046@naomi.webworks.nl>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: disposed ComponentLocator
Thread-Index: AcL0n7ZIwnUv94+UQHWDvGHP4TD3KQAbcKCA
From: "Unico Hommes" <Unico@hippo.nl>
To: <cocoon-dev@xml.apache.org>
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

=20

>=20
> -----Original Message-----
> From: Jeremy Quinn [mailto:jeremy@media.demon.co.uk]=20
> Sent: donderdag 27 maart 2003 21:30
> To: cocoon-dev@xml.apache.org
>=20
> Hi All
>=20
> With yesterday's CVS, I am getting this error ... after a while:
>=20
>=20
>=20
>=20
> Internal Server Error
>=20
> Message: You cannot lookup components on a disposed ComponentLocator
>=20
> Description: java.lang.IllegalStateException: You cannot=20
> lookup components on a disposed ComponentLocator
>=20

<snip />


>=20
>=20
> Apache Cocoon 2.1-dev
>=20
>=20
> Anyone seen anything like it?
>=20

Yes I've seen this some time ago. I was using the then CVS HEAD version
of Excalibur-Component instead of the one delivered with Cocoon and saw
this exception after editing a sub-sitemap. My guess was that something
had changed in Component that made it incompatible with Cocoon. I was
under the impression that subsequent changes to Component had fixed
this.