Mailing-List: contact log4j-dev-help@logging.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Log4J Developers List" <log4j-dev@logging.apache.org>
Date: Sat, 12 Jun 2010 02:22:07 -0400 (EDT)
Message-Id: <201006120622.o5C6M7It003734@thor.apache.org>
From: bugzilla@apache.org
To: log4j-dev@logging.apache.org
Subject: DO NOT REPLY [Bug 49421] Chainsaw don't show Logger for
 SocketReceiver and SocketHubReceiver
In-Reply-To: <bug-49421-31091@https.issues.apache.org/bugzilla/>
References: <bug-49421-31091@https.issues.apache.org/bugzilla/>
Auto-Submitted: auto-generated
Content-Type: text/plain; charset="UTF-8"
MIME-Version: 1.0

https://issues.apache.org/bugzilla/show_bug.cgi?id=49421

--- Comment #2 from Scott Deboy <sdeboy@iname.com> 2010-06-12 02:22:05 EDT ---
Fix committed to Chainsaw (and receivers) svn head, revision 953945.

Commit msg:
Fix Bug 49421:  Chainsaw don't show Logger for SocketReceiver and
SocketHubReceiver

All calls to the LoggingEvent constructor which pass in another event's Logger
may only have a categoryName field and not logger field available - updated
calls to LoggingEvent constructor to ensure logger was passed in if not null,
or a logger was created from the logger name (pre-existing bug in rewritepolicy
classes if they were used with socketappender/receiver).

Also (arbitrarily) updated Chainsaw revision in the pom.xml 2.1.0, in order to
keep folks from being confused that this latest version is the original 2.0
(which according to maven was previously 1.99)

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org