On Wed, 10 Jul 2002 19:55, Carsten Ziegeler wrote: > > This should not harm cocoon as I null it out if useStore is > > false. At leats > > thats what I thought, though I could be wrong ? :) > > No, it doesn't do any harm directly - but it > a) requires to declare also the store component, even if > it is not used (= optional)
I am not sure I understand this - why do you need to declare it? If it is not declared then hasComponent() should return false I thought. Thus you will never attempt to lookup component if it is not declared. > b) is a (minor) performance problem as the (costly) lookup > mechanism is always used. Is this an issue? If so I will revert it. But given the number of other lookups I figure it was a negligable amount of the whole components lifecycle. Especially as it is looking up ThreadSafe components. SO should I revert? -- Cheers, Peter Donald --------------------------------------------------- Murphy's law - "Anything that can go wrong, will." (Actually, this is Finagle's law, which in itself shows that Finagle was right.) --------------------------------------------------- -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
