I was playing around with LTK Java today, and it appears that some
classes (I suspect those that are in the org.ltk.llrp.generated package)
do not use their fully qualified class name as their log4j logger. This
makes it more difficult to reduce logging output from those classes. To
filter the output from the other classes, I can do something like this
in my log4j.properties file:
log4j.category.org.llrp.ltk=ERROR
However, I am still seeing output from generated classes, because it
appears their loggers are simply their class names.
I don't know if there is another way to catch this in log4j, and this
certainly isn't a big problem...Just wondering if it could be fixed for
the next point release.
Thanks,
Kyle Neumeier
------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
llrp-toolkit-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/llrp-toolkit-devel
