giacomo wrote: > > On Fri, 10 Aug 2001, giacomo wrote: > > Ok, lets summarize: > > The goal: > > Enable configurability of the Logger a Component > will receive by the ComponentMananger. > > Proposed is a magic attribute logger (same approach take for the > pool-min, pool-max attributes to Poolable Components) that references > the logger to use: > > <component role="MyComp" class="..." logger="file"/> > > A possible solution seems to be a similar approach take for the roles > definitions (RoleManager). > > So the LogKit configuration file (see proposals below) will be fed into > a LogKitManager (Configurable). This LogKitManager creates the > Categories, LogTargets, and Filters. To enable the specified > LogTargetFactories to create LogTargets like ServletLogTarget a Context > object might be needed so the LogKitManager must and the > LogTargetFactories could be Contextualizable. All classes mentioned so > far will be Loggable to report failures during setup. The Logger will be > the one passed in by the client class as usual (probabbly the root > logger). > > After initialisation of this LogKitManager it is passed to the > ExcaliburComponentManager (setLogKitManager). This is optional. The > ExcaliburCM must be extended to interpret the magic attributes mentioned > above in case a LogKitManager was set. The magic attribute denotes the > logger to used received from the LogKitManager and passed to the > Component in question. > > Does this satisfy all your needs you have?
It satisfies mine, and I believe it satisfies Cocoon's needs as well. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
