Peter Donald wrote: > > > > > Why do you want to aquire the store even if it is not used? > > Basically to avoid warnings in a container I am working on. ie If > you declare > dependencies (even if they are optional dependencies) and the container > provides you component but you dont use it then the container > will wanr you > saying something like > > "You have misdeclared a dependency on X as it was never used." > > or similar. > Hmmm, I'm not sure if this is a good feature - because an optional dependency means it's - well - optional. And I see two use cases their: a) The optional component is only used if it is available b) The optional component is used only in some circumstances
But in neiter of the two cases, the optional component should only be looked up if it is required. > 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) b) is a (minor) performance problem as the (costly) lookup mechanism is always used. Carsten -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
