Sascha Brawer wrote:
> Sounds great. But you don't need to define a custom Level for this
> purpose, it's already in the framework.
>
> Just use java.util.logging.Logger.getLogger("java.awt") to
> create/retrieve a Logger for java.awt. The framework maintains a tree
> of Loggers, and passes up LogRecords to the parent logger by default.
> That is, a logger of "java.awt.image.jpeg" will by default forward
> LogRecords to the logger for "java.awt.image", which will in turn
> forward it to its parent, and so on.
>Yeah, that's another way to do it. I'd only be concerned about how over-flexible that approach is for this usage, and whether or not it would be a burden to use -- would you have to add half a dozen -D options, or go edit a properties file? I kind of like being able to specify a simple comma-delineated list of components to log into one property. Also, what would the performance impact be if we used trees of loggers, and not a simple filter with a bit set? Cheers,
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Classpath mailing list [email protected] http://lists.gnu.org/mailman/listinfo/classpath
