cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ovidiu Predescu <>
Subject latest Excalibur bites back
Date Tue, 02 Apr 2002 21:23:15 GMT
After the last cvs update I've done, the newly updated Excalibur
started to show some of the old problems I've seen in the past. The
problem is that essentially components defined in cocoon.xconf cannot
be looked up anymore, and generate a "Could not find component"
exception. Cocoon seems to be working fine, but Schecoon is currently

Can somebody explain how the lookup mechanism in Excalibur changed
since the 4.1 release?


To unsubscribe, e-mail:
For additional commands, email:

View raw message