> 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:
DEBUG (2001-11-28) 13:59.11:161 [cocoon ] (/edit-repository/home/archiv/Development/)
Could not find component for role:
org.apache.cocoon.components.saxconnector.SAXConnectorjava.lang.NullPointerException
at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1220)
at java.lang.ClassLoader.loadClass(ClassLoader.java:290)
at java.lang.ClassLoader.loadClass(ClassLoader.java:253)
at
org.apache.avalon.excalibur.component.ExcaliburComponentManager.lookup(ExcaliburComponentManager.java:273)
at
org.apache.avalon.excalibur.component.ExcaliburComponentManager.hasComponent(ExcaliburComponentManager.java:140)
at
org.apache.cocoon.components.pipeline.AbstractEventPipeline.compose(AbstractEventPipeline.java:61)
...
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
