Jeff Turner wrote:
On Mon, Jan 20, 2003 at 12:34:04AM -0600, Antonio Gallardo wrote:This change is in the 2.1, which is still "pre-alpha", even if it the code is largely stable. Version numbers change will occur when entering the beta stage.
Hi!Oh.. I was getting those errors too :) I found it was because my sitemap used
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.
'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..
Now you're right that the error message doesn't really help in diagnosing the problem. I'll take a look at it.
Sylvain
--
Sylvain Wallez Anyware Technologies
http://www.apache.org/~sylvain http://www.anyware-tech.com
{ XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects }
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
