Just a minor observation - shouldn't Level.toLocationAwareLoggerInteger(Level level) be a static method (like its counterpart fromLocationAwareLoggerInteger)? Best regards, Richard Sand | Managing Director PO Box 91824 | Austin | Texas 78709-1824 | USA Office: +1 888 612 8820 ext 02 | Fax: +1 866 304 3754 Mobile: +1 267 984 3651
Just a minor observation - shouldn't Level.toLocationAwareLoggerInteger(Level level) be a static method (like its counterpart fromLocationAwareLoggerInteger)? Best regards, Richard Sand | Managing Director PO Box 91824 | Austin | Texas 78709-1824 | USA Office: +1 888 612 8820 ext 02 | Fax: +1 866 304 3754 Mobile: +1 267 984 3651
The question for me would be "why does toLocationAwareLoggerInteger take a Level as a parameter?". I would expect it to be non-static but take no parameters and act on the instance it was called upon. ----- Original Message -----
From: "Richard Sand" <rsand@idfoundry.com> To: "logback users list" <logback-user@qos.ch> Sent: Tuesday, 12 February, 2013 7:36:19 PM Subject: [logback-user] Level.toLocationAwareLoggerInteger Just a minor observation - shouldn't Level.toLocationAwareLoggerInteger(Level level) be a static method (like its counterpart fromLocationAwareLoggerInteger)?
Best regards,
Richard Sand | Managing Director PO Box 91824 | Austin | Texas 78709-1824 | USA Office: +1 888 612 8820 ext 02 | Fax: +1 866 304 3754 Mobile: +1 267 984 3651 _______________________________________________ Logback-user mailing list Logback-user@qos.ch http://mailman.qos.ch/mailman/listinfo/logback-user
participants (2)
-
Richard Sand -
Robert Elliot