cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stuart Roebuck <>
Subject Problems with my.roles going from 2.0.2 to 2.0.3
Date Wed, 12 Jun 2002 20:50:43 GMT
In order to resolve some problems in 2.0.2 and accommodate the changes 
in SourceResolvers between 2.0.2 and 2.0.3 I have moved my project to 
the latest 2.0.3 CVS and I'm now having problems using one of my own 
non-sitemap components that was working fine in 2.0.2.

I've done a complete clean build of my own classes and 2.0.3.

My 'my.roles' file is being found okay, if I move it I get a file not 
found error on it.

My Component is being 'composed' correctly.

But the first time I use it I get:

> org.apache.avalon.framework.component.ComponentException: Could not 
> find component
>         at 
> org.apache.avalon.excalibur.component.ExcaliburComponentManager.lookup
> (
>         at 
> org.apache.cocoon.components.CocoonComponentManager.lookup
> (
>         at 
> org.apache.avalon.excalibur.component.DefaultComponentFactory$ComponentManagerProxy.
> lookup(
>         at 
> org.apache.avalon.excalibur.component.DefaultComponentFactory$ComponentManagerProxy.
> lookup(

Any thoughts of anything that could have changed between 2.0.2 and 2.0.3 
that would require a change to my component?  Is there anything more 
strict about registration of components or interface changes that would 
not show up as compile errors.


            Public Key - 1024D/88DD65AF 2001-11-23 Stuart Roebuck (Adolos)
      Key fingerprint = 89D9 E405 F8B1 9B22 0FA2  F2C1 9E57 5AB1 88DD 65AF
Stuart Roebuck                        
Systems Architect                             Java, XML, MacOS X, XP, 
ADOLOS                                           <>

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

View raw message