cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Antonio Gallardo" <agalla...@agsoftware.dnsalias.com>
Subject Re: [Bug 16248] New: - Reloading a modified page causes NPE
Date Mon, 20 Jan 2003 18:16:39 GMT
Stefano Mazzocchi dijo:
> Jeff Turner wrote:
>> 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?
>
> no, because these things were never released anyway.
>
>> Users are NOT going to be amused
>> when all their sitemaps break with such an unhelpful message..
>
> Read the WARNING.txt file on the xml-cocoon2 CVS module.
>
> Once we exit alpha stage, those things won't change, but now it's hard
> enough to come up with a serious design without having to back-support
> anything that gets tried out.
>
> The reason why we don't release anything right now is *exactly* to
> prevent those issues and protect our users.
>
> Besides, we had a vote on that change that passed and you didn't vote -1
>  on it. I think it's very unfair to complain on it afterwards.
>
> --
> Stefano Mazzocchi                               <stefano@apache.org>
> --------------------------------------------------------------------

Hi Stefano:

Sorry about the problem. It was my fault. But anyway, I think we need to
put a little better error description than:

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.

Please take the advise in the good sense. And lets continue this good job
called Cocoon.

I will continue being a alpha-beta to gamma tester of Cocoon. I enjoy to
see the new features and trying it.

By the wat the new cache system + XSLTC is amazing faster! I am impresed
of it speed with XSP.

Best Regards,

Antonio Gallardo




---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message