2013/7/22 Durchholz, Joachim <[email protected]>
> > True, fixing namespaces to be more concise might render > > #2622 obsolete. > > Agreed. > > > Or - more likely - the two features might complement > > each other, if they're well-designed. > > I doubt there's a better design waiting to be discovered. > Logging is a topic that has been worked on by the Apache folks and Ceki > Gülcü. There's no detail improvement waiting to happen in that area that > they haven't thought about (or been asked to do) in the past. > Good point. > To the very least, I'd fly any ideas by those guys just to see the > comments from the masters of the field. > > > Usually, when specifying logging levels in a logger > > configuration, you're doing that for the whole system. > > Sometimes, you want to enable logging just for an "area" > > in your application - e.g. the payment module, which can > > then use a different Configuration from the other modules. > > I tend to do that by reconfiguring the logger in question from the code - > crank up the logging level on entry and restore it on exit. > It's a bit inconvenient, but the use case doesn't seem to be so frequent > that people are really asking for it. > > But... well... I guess anybody's experience is limited to personal > experience. > I'd still ask the logging gurus, not because they're smart but because > more people have contacted them about their use cases so the gurus know > what's really needed and where the workarounds are good enough. > Fair enough, I'll do that eventually. -- You received this message because you are subscribed to the Google Groups "jOOQ User Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
