Further proof, for me at least, that the properties file format is more 
confusing than the xml file format.  I use log4j's successor, logback, and I'm 
so glad that it doesn't support the properties file format for configuration.


Zaske wrote:
> Thanks Toby!
> It did the trick!
> Here is my complete logging.properties file:
> 
> .level = WARN
> 
> # Set the default logging level for ORM, specifically, to WARNING
> DataNucleus.JDO.level=WARNING
> DataNucleus.Persistence.level=WARNING
> DataNucleus.Cache.level=WARNING
> DataNucleus.MetaData.level=WARNING
> DataNucleus.General.level=WARNING
> DataNucleus.Utility.level=WARNING
> DataNucleus.Transaction.level=WARNING
> DataNucleus.Datastore.level=WARNING
> DataNucleus.ClassLoading.level=WARNING
> DataNucleus.Plugin.level=WARNING
> DataNucleus.ValueGeneration.level=WARNING
> DataNucleus.Enhancer.level=WARNING
> DataNucleus.SchemaTool.level=WARNING
> com.zas.test.level=INFO
> 
> 
> On Nov 13, 9:02 am, Toby Reyelts <to...@google.com> wrote:
>> Did you try com.zas.test.level=INFO instead of com.zas.test=INFO ?
>>
>> On Fri, Nov 13, 2009 at 1:22 AM, Zaske <yair.zaslav...@gmail.com> wrote:
>>> Yes, I tried filtering info - and did not get the messsage.
>>> In the end I changed the file to look like:
>>> .level = FINEST
>>> # Set the default logging level for ORM, specifically, to WARNING
>>> DataNucleus.JDO.level=WARNING
>>> DataNucleus.Persistence.level=WARNING
>>> DataNucleus.Cache.level=WARNING
>>> DataNucleus.MetaData.level=WARNING
>>> DataNucleus.General.level=WARNING
>>> DataNucleus.Utility.level=WARNING
>>> DataNucleus.Transaction.level=WARNING
>>> DataNucleus.Datastore.level=WARNING
>>> DataNucleus.ClassLoading.level=WARNING
>>> DataNucleus.Plugin.level=WARNING
>>> DataNucleus.ValueGeneration.level=WARNING
>>> DataNucleus.Enhancer.level=WARNING
>>> DataNucleus.SchemaTool.level=WARNING
>>> com.zas.test=INFO
>>> That is  - I changed the default logging level to FINEST.
>>> I dont like this solution - it's not a "clean solution" and does not
>>> remind me the log4j usage I'm used to.
>>> I would still appreciate if someone can help me fully understand this.
>>> On Nov 13, 1:54 am, Rusty Wright <rwright.li...@gmail.com> wrote:
>>>> 1) Appcfg gets the request (access) logs, not the error logs.
>>>> 2) On the web page console, did you change the filtered log level to
>>> INFO?  It starts out filtering for ERROR or WARN.
>>>> Zaskewrote:
>>>>> Hi all,
>>>>> I want to log (at INFO level) all classes that their package begin
>>>>> with com.zas.test -
>>>>> For this I added the line:
>>>>> com.zas.test=INFO
>>>>> to my logging.properties file - so now it looks like this:
>>>>> .level = WARNING
>>>>> # Set the default logging level for ORM, specifically, to WARNING
>>>>> DataNucleus.JDO.level=WARNING
>>>>> DataNucleus.Persistence.level=WARNING
>>>>> DataNucleus.Cache.level=WARNING
>>>>> DataNucleus.MetaData.level=WARNING
>>>>> DataNucleus.General.level=WARNING
>>>>> DataNucleus.Utility.level=WARNING
>>>>> DataNucleus.Transaction.level=WARNING
>>>>> DataNucleus.Datastore.level=WARNING
>>>>> DataNucleus.ClassLoading.level=WARNING
>>>>> DataNucleus.Plugin.level=WARNING
>>>>> DataNucleus.ValueGeneration.level=WARNING
>>>>> DataNucleus.Enhancer.level=WARNING
>>>>> DataNucleus.SchemaTool.level=WARNING
>>>>> com.zas.test=INFO
>>>>> At my code I tried this:
>>>>> private static final Logger log = Logger.getLogger("com.zas.test");
>>>>> and then later on:
>>>>>  log.info("Test logging");
>>>>> When using appcfg to retrieve the logs or viewing them using the
>>>>> administration consoleI did not see the "Test logging" message.
>>>>> The name of my servlet class is TestServlet (under package
>>>>> com.zas.test.googleapp.server), so I also tried obtaining the logger
>>>>> object like this:
>>>>> private static final Logger log = Logger.getLogger
>>>>> (TestServlet.class.getName());
>>>>> But still, failed to log.
>>>>> Can you please explain me what I'm doing wrong?
>>>>> --
>>>>> 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-j...@googlegroups.com.
>>>>> To unsubscribe from this group, send email to
>>> google-appengine-java+unsubscr...@googlegroups.com<google-appengine-java%2bunsubscr...@googlegroups.com>
>>> .
>>>>> For more options, visit this group athttp://
>>> groups.google.com/group/google-appengine-java?hl=.
>>> --
>>> 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-j...@googlegroups.com.
>>> To unsubscribe from this group, send email to
>>> google-appengine-java+unsubscr...@googlegroups.com<google-appengine-java%2bunsubscr...@googlegroups.com>
>>> .
>>> For more options, visit this group at
>>> http://groups.google.com/group/google-appengine-java?hl=.
>>
> 
> --
> 
> 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-j...@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=.
> 
> 

--

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-j...@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=.


Reply via email to