cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Berin Loritsch <blorit...@apache.org>
Subject Re: why many messages: Could not find component
Date Wed, 28 Nov 2001 14:15:58 GMT
Stefan Koehler wrote:

>>When I implemented this test, the ComponentManager didn't support checking
>>if a component is available or not. But in a later version the
>>"hasComponent()" method
>>was added to the ComponentManager, but unfortunately we forgot about
>>changing our code. I fixed this ten minutes ago.
>>
>>Carsten
>>
> 
> Thanks for the fix. But unfortunately it doesn't solve the stacktrace-in-the-log-
> problem.  Even the hasComponent() check produces unwanted log messages:


That would be a change to the ExcaliburComponentManager.  You'll have to wait
for that, as I would have to do the change, and then you would have to wait for
Cocoon to incorporate it...


-- 

"Those who would trade liberty for
  temporary security deserve neither"
                 - Benjamin Franklin


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message