I'm experiencing the problem with a modified version of the 1.0.4 code. I
haven't been able to build the CVS version on WinNT, where I'm having the
problem, but I didn't see anything in the CVS source that would change this
behavior.
We discussed earlier how supplying the FQN to the Category would fix "the
problem." But back then, "the problem" had to do with the case where
l7dlog was overridden by the Category subclass. When the Category.l7dlog
was changed to call forcedLog, making the override unnecessary, the stack
trace changed. The subcategory is no longer the last entry before the
caller. Rather, the category log method is. At my customer site, I've
fixed this locally by changing the subcategory constructor to NOT alter the
instanceFQN (which is only possible with the 1.0.4 version since the needed
constructor is not available in the present CVS version).
Does this seem correct? I won't be able to verify the current CVS behavior
for sure until I either get home to build it on Linux or learn Ant for NT
(which I'm working on).
- Paul
Paul Glezen
IT Specialist
WebSphere Engagement Team
Tel: 818 539 3321
[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
