On Mon, Jan 20, 2003 at 12:34:04AM -0600, Antonio Gallardo wrote:
> Hi!
>
> I can confirm that the new cache implementation is a little buggy. I was
> the last 5 days trying to make run my application (that is already tested)
> in the lastest CVS.
>
> I am another error with the new cache interface. I dont know where is the
> problem. Throw an exception about some UnnamedSelector:
>
> ERROR (2003-01-14) 17:12.17:171 [core.manager] (/myapp/aut-inicio)
> > Thread-7/ExcaliburComponentSelector: UnnamedSelector: ComponentSelector
> > Attempted to retrieve component with null hint.
Oh.. I was getting those errors too :) I found it was because my sitemap used
'map:pipelines' inside map:components, and the syntax recently changed to
'map:pipes':
<map:components>
...
<map:pipes default="caching">
<map:pipe name="caching"
src="org.apache.cocoon.components.pipeline.impl.CachingProcessingPipeline"/>
<map:pipe name="noncaching"
src="org.apache.cocoon.components.pipeline.impl.NonCachingProcessingPipeline"/>
</map:pipes>
</map:components>
Erm. Shouldn't the sitemap version be incremented for large
backwards-incompatible changes like this? Users are NOT going to be amused
when all their sitemaps break with such an unhelpful message..
--Jeff
<snip/>
>
> Best Regards,
>
> Antonio Gallardo
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
