[appengine-java] Re: Log4J vs. java.util.logging in App Engine projects
Hi Bill, Would you mind filing an issue for this: http://code.google.com/p/googleappengine/issues/list Thanks, Rajeev On Tue, Sep 1, 2009 at 10:12 PM, Bill Higgins billh...@gmail.com wrote: Thanks again for the explanation Rajeev. I would politely suggest beefing up the header comments in the log4j.properties file and the logging.properties, explaining to the user that they may either use Log4J or java.util.logging as they please. On Sep 1, 11:09 am, Rajeev Dayal rda...@google.com wrote: Yes, I think you've got it exactly right. If you notice any deviations from this behavior, please post back on this thread and let us know. On Tue, Sep 1, 2009 at 9:31 AM, Bill Higgins billh...@gmail.com wrote: Thanks much for the response Rajeev. Let me see if I can repeat and reduce it to make sure I understand the formula. 1) DataNucleus will use EITHER log4j OR java.util.logging. It never uses both. 2) DataNucleus will use log4j if it detects log4j classes on the classpath, otherwise it will use java.util.logging 3) If my app doesn't use log4j, then I can safely delete the default log4j.properties file and DataNucleus will happily use java.util.logging Is this correct? On Aug 31, 5:22 pm, Rajeev Dayal rda...@google.com wrote: +[tobyr] Hi Bill, We include both logging files due to the implementation of Datanucleus. If you have log4j on your classpath (or if you have any jars which bundle the log4j classes), then Datanucleus will use the log4j logging system. If you don't have a configuration file for log4j, then none of the information will be displayed. That is why we include one by default. If you do not have log4j on your classpath, then the log4j system is not used, and neither is the log4j.properties file which we include. If you are sure that you do not have any log4j classes on your classpath, then you can safely remove the log4j.properties file, and control all of your logging via the logging.properties file. If you're using log4j, you can get rid of the logging.properties file. My recommendation would be to keep both files, and only update the one for the logging system that you're using. You don't need to keep both of them in sync unless you adjust the Datanucleus logging levels. Let me know if you have any questions - I know that this is somewhat confusing. Rajeev On Sun, Aug 30, 2009 at 7:51 AM, Bill Higgins billh...@gmail.com wrote: Hi, I'm new to App Engine development, and am a bit confused by the logging configuration files that the Google Eclipse project produces in a new web application project. When you create a new web app project, the new project includes two logging configuration files: project/src/log4j.properties project/war/WEB-INF/logging.properties I understand that the first is for log4j and the second for java.util.logging but I'm not sure why one would need both and how each affect logging determinations. If I make changes to one should I make changes to another? Is there a safe way to delete one and simply use the other? If so which one is the keeper? Thanks in advance. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google App Engine for Java group. To post to this group, send email to google-appengine-java@googlegroups.com To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en -~--~~~~--~~--~--~---
[appengine-java] Re: Log4J vs. java.util.logging in App Engine projects
Thanks much for the response Rajeev. Let me see if I can repeat and reduce it to make sure I understand the formula. 1) DataNucleus will use EITHER log4j OR java.util.logging. It never uses both. 2) DataNucleus will use log4j if it detects log4j classes on the classpath, otherwise it will use java.util.logging 3) If my app doesn't use log4j, then I can safely delete the default log4j.properties file and DataNucleus will happily use java.util.logging Is this correct? On Aug 31, 5:22 pm, Rajeev Dayal rda...@google.com wrote: +[tobyr] Hi Bill, We include both logging files due to the implementation of Datanucleus. If you have log4j on your classpath (or if you have any jars which bundle the log4j classes), then Datanucleus will use the log4j logging system. If you don't have a configuration file for log4j, then none of the information will be displayed. That is why we include one by default. If you do not have log4j on your classpath, then the log4j system is not used, and neither is the log4j.properties file which we include. If you are sure that you do not have any log4j classes on your classpath, then you can safely remove the log4j.properties file, and control all of your logging via the logging.properties file. If you're using log4j, you can get rid of the logging.properties file. My recommendation would be to keep both files, and only update the one for the logging system that you're using. You don't need to keep both of them in sync unless you adjust the Datanucleus logging levels. Let me know if you have any questions - I know that this is somewhat confusing. Rajeev On Sun, Aug 30, 2009 at 7:51 AM, Bill Higgins billh...@gmail.com wrote: Hi, I'm new to App Engine development, and am a bit confused by the logging configuration files that the Google Eclipse project produces in a new web application project. When you create a new web app project, the new project includes two logging configuration files: project/src/log4j.properties project/war/WEB-INF/logging.properties I understand that the first is for log4j and the second for java.util.logging but I'm not sure why one would need both and how each affect logging determinations. If I make changes to one should I make changes to another? Is there a safe way to delete one and simply use the other? If so which one is the keeper? Thanks in advance. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google App Engine for Java group. To post to this group, send email to google-appengine-java@googlegroups.com To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en -~--~~~~--~~--~--~---
[appengine-java] Re: Log4J vs. java.util.logging in App Engine projects
Yes, I think you've got it exactly right. If you notice any deviations from this behavior, please post back on this thread and let us know. On Tue, Sep 1, 2009 at 9:31 AM, Bill Higgins billh...@gmail.com wrote: Thanks much for the response Rajeev. Let me see if I can repeat and reduce it to make sure I understand the formula. 1) DataNucleus will use EITHER log4j OR java.util.logging. It never uses both. 2) DataNucleus will use log4j if it detects log4j classes on the classpath, otherwise it will use java.util.logging 3) If my app doesn't use log4j, then I can safely delete the default log4j.properties file and DataNucleus will happily use java.util.logging Is this correct? On Aug 31, 5:22 pm, Rajeev Dayal rda...@google.com wrote: +[tobyr] Hi Bill, We include both logging files due to the implementation of Datanucleus. If you have log4j on your classpath (or if you have any jars which bundle the log4j classes), then Datanucleus will use the log4j logging system. If you don't have a configuration file for log4j, then none of the information will be displayed. That is why we include one by default. If you do not have log4j on your classpath, then the log4j system is not used, and neither is the log4j.properties file which we include. If you are sure that you do not have any log4j classes on your classpath, then you can safely remove the log4j.properties file, and control all of your logging via the logging.properties file. If you're using log4j, you can get rid of the logging.properties file. My recommendation would be to keep both files, and only update the one for the logging system that you're using. You don't need to keep both of them in sync unless you adjust the Datanucleus logging levels. Let me know if you have any questions - I know that this is somewhat confusing. Rajeev On Sun, Aug 30, 2009 at 7:51 AM, Bill Higgins billh...@gmail.com wrote: Hi, I'm new to App Engine development, and am a bit confused by the logging configuration files that the Google Eclipse project produces in a new web application project. When you create a new web app project, the new project includes two logging configuration files: project/src/log4j.properties project/war/WEB-INF/logging.properties I understand that the first is for log4j and the second for java.util.logging but I'm not sure why one would need both and how each affect logging determinations. If I make changes to one should I make changes to another? Is there a safe way to delete one and simply use the other? If so which one is the keeper? Thanks in advance. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google App Engine for Java group. To post to this group, send email to google-appengine-java@googlegroups.com To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en -~--~~~~--~~--~--~---
