Claude Brisson said: > Since there are big chances that all the instances do log to the > same place, option #1 is definitely not a good choice. Should > option #2 or #3 be choosen, it is important to have a static access > to logging. > > With #2, can't you have c-l default configuration redirecting > towards the Velocity log ?
no, i feel pretty strongly that configuring/redirecting c-l output is not something that a component (e.g. veltools) should take upon itself. if we take this option, then the user would have to configure c-l to use LogSystemCommonsLog on their own. the most we could do is have the VVS tell the LogSystemCommonsLog to use its particular VelocityEngine for all output (instead of the singleton) just in case the user decides to point c-l in that direction. > Otherwise, I guess #3 is okay, it is more or less unavoidable to > have chained logging adapters when using several packages. ... yeah, it's okay, and i did get a test of this option working. but after trying it out, i think i like #2 a wee bit more. Nathan Bubna [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
