See https://issues.apache.org/jira/browse/OFBIZ-5207
Jacques From: "Jacques Le Roux" <[email protected]> > Just a quick and last note: > > 1) to get back the behaviour we had in R4.0, you need to set in Debug.java > the levelObjs[1] value to the level you want. We could make that dynamic > Webtools Log Configuration. But I don't think anybody really wants that back > (too much infomation kills the information). > 2) I did not find a way to dynamically set the the level of a class or > package, without enabling the whole others at the same level (using > levelObjs[1] value). So I decided I will use the <<if (Debug.verboseOn()) > Debug.logAnyLevelHere(....)>> when needed. > > So should we change the misleading UI in Webtools Log Configuration? How are > you currently using it? If you have any ideas or suggestions please share > > Jacques > > > From: "Jacques Le Roux" <[email protected]> >> As I thought, this was working in R4.0 >> >> Though, let me clarify "this": >> * Setting, dynamically or not, the verbose level, you get all Debug.log() >> levels lines in log, including lower levels like DEBUG (I clearly remembered >> having used it in 2007 and I'm quite sure since but not when) >> * If verbose is not set, adding a logger for a class or package with ALL >> level does not work. You don't see the verbose lines of this class/package >> >> What I want: see only Debug.logVerbose lines for a class or package, I don't >> want to see all Debug.log() levels lines. I thought this was working but I >> must say I never got to get it working. >> >> I will digg in changes since then. Because having at least the verbose >> option working is necessary. In the meantime we can use >> >> if (Debug.verboseOn()) Debug.logInfo(....) >> >> but it's not quite satisfactory, though I will maybe not have the time to do >> better :D >> >> If someone remember something please chime in... >> >> Jacques >> >> From: "Jacques Le Roux" <[email protected]> >>> Hi, >>> >>> I wonder about something. If, in Webtools Log Configuration, I check all >>> debugging levels (ie add verbose to OOTB default). I don't get verbose >>> lines in log. >>> >>> For instance I tried locally with trunk by running the getPartyFromEmail >>> using [email protected]. I see the line >>> >>> 2013-05-08 17:03:02,218 (http-bio-0.0.0.0-8443-exec-18) [ >>> PartyServices.java:762:INFO ] PartyFromEmail number found: 23 >>> >>> but not the PartyServices.java:761 line just above (verbose) >>> >>> This is not related to the dynamic part of it. The same happens if you set >>> print.verbose=true in debug.properties >>> >>> I checked with Eclipse debugger and all seems to works well but when you >>> get to >>> >>> logger.log(callingClass, levelObjs[level], msg, t); >>> >>> in Debug.java, the verbose calls are not printed in log >>> >>> I also tried in webtools log config to add a org.ofbiz.party.party logger, >>> and even org.ofbiz.party.party.PartyServices, set to DEBUG or ALL, and to >>> use -DDEBUG=true system property to no avail. >>> >>> Do I miss or misunderstand something? In other words, how do you set the >>> system to get the Debug.logVerbose() to print stuff in log? >>> Particularly only for a package or class. This is, for instance, to avoid >>> printing all verbose lines but in a class. >>> >>> I barely checked the situation is the same from R9.04 included >>> >>> Any ideas? >>> >>> Thanks >>> >>> Jacques >>> >>> >> >
