Timeline for Can one Java Application use log4j for logging one class and util logging for another class?
Current License: CC BY-SA 3.0
13 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 5, 2018 at 9:51 | audit | Suggested edits | |||
| Jan 5, 2018 at 9:51 | |||||
| Dec 17, 2017 at 13:24 | comment | added | DodgyCodeException | @Kayaman sorry, I disagree. In my experience, I've seen many experienced developers use java.util.logging. Firstly because, when you create a Java application for an end-user, you don't have to supply additional dependent jars. Secondly because later releases of java.util.logging have a nicer API than, for example, slf4j (using printf-like parameter syntax rather than the unintuitive and inflexible "{}"). | |
| Dec 17, 2017 at 12:27 | comment | added | Kayaman |
@DodgyCodeException it has never been about performance but the design flaws in it. An experienced developer would never use java.util.logging.
|
|
| Dec 15, 2017 at 16:44 | comment | added | DodgyCodeException | @Kayaman Using java.util.logging is not stupid and the link you refer to in support of not using it is now quite out of date. Java util logging has come a long way recently with the addition of new Java 8 features which means that it now performs very well. | |
| Dec 9, 2017 at 16:03 | comment | added | tkruse | Provide a minimal code/configuration example that others can run to reproduce your problem. | |
| Dec 8, 2017 at 10:53 | comment | added | Mathjoh | @Dheeraj As the different logging classes have their own configuration they should be able to feed their logs to the same output. So unless you overwrite come config for when when you do the other it should work right out the box. If the problem is configuring util logging after log4j, have you tried change the order in which you load the configs? | |
| Dec 8, 2017 at 10:52 | comment | added | Kayaman | You might want to reconsider your standards. See for example stackoverflow.com/questions/11359187/… | |
| Dec 8, 2017 at 10:30 | comment | added | Dheeraj | @Kayaman: Yes, it is forced as it is considered a standard for logging application logs in my project. | |
| Dec 8, 2017 at 9:46 | comment | added | Kayaman |
It's possible, but stupid. Interestingly enough, using java.util.logging itself is quite stupid, so unless you're forced for some unknown reason to use it, don't.
|
|
| Dec 8, 2017 at 9:34 | comment | added | Dheeraj | @Mathjoh: I've added a little more detail now. | |
| Dec 8, 2017 at 9:33 | history | edited | Dheeraj | CC BY-SA 3.0 |
added detail
|
| Dec 8, 2017 at 9:16 | comment | added | Mathjoh | It is definitively be possible to do both. You should add how you configure your logging to the question. Do you use code, xml or .properties? And how is your configuration loaded? | |
| Dec 8, 2017 at 9:12 | history | asked | Dheeraj | CC BY-SA 3.0 |