Quoting rufio <[EMAIL PROTECTED]>: > on Thu, 21 Aug 2003 12:26:46 -0400 Geoff Howard <[EMAIL PROTECTED]> > wrote: > > > the ComponentSelector has nothing to do with the map:selector and > > family. Probably this error means that you forgot to define a default > > generator, etc. and have pipelines which depend on the definition of a > > default. > > Thanx for the hint I asked for. > I copied whole <map:components/> from the original sitemap.xmap so it > won't cause problems. > > Does having unused components have impact on performance? or maybe just > compile time of sitemap?
I have not tested this but my understanding is that having unused components can needlessly increase startup time and will take more memory. This is based ont the pool-min attribute. At startup, this should cause the container to create exactly pool-min instances of each of those components, even ones you never reference. I may be wrong, so if you feel like putting together a test I'd be grateful for the confirmation/correction. Your problem though was probably only related to one component. You can still disable all the ones you don't use, you just need to make sure you account for it everywhere you need to. Feel free to ask for specific help doing this, but you'll need to provide more specific details. Geoff --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
