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: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
