Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-dev@ws.apache.org
Message-ID: <32026946.1174465892655.JavaMail.jira@brutus>
Date: Wed, 21 Mar 2007 01:31:32 -0700 (PDT)
From: "David Illsley (JIRA)" <jira@apache.org>
To: axis-dev@ws.apache.org
Subject: [jira] Resolved: (AXIS2-2359) PERF:
 AddressingOutHandler.WSAHeaderHandler does not need its own logger
In-Reply-To: <18859304.1174465412140.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/AXIS2-2359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Illsley resolved AXIS2-2359.
----------------------------------

    Resolution: Fixed

Fixed in SVN r520799

> PERF: AddressingOutHandler.WSAHeaderHandler does not need its own logger
> ------------------------------------------------------------------------
>
>                 Key: AXIS2-2359
>                 URL: https://issues.apache.org/jira/browse/AXIS2-2359
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: Addressing
>            Reporter: David Illsley
>         Assigned To: David Illsley
>            Priority: Minor
>
> PERF: AddressingOutHandler.WSAHeaderHandler does not need its own logger
> Profiling the AddressingOutHandler shows that because the logger in the inner class cannot be static there's a lot of class caching going on. Simple fix: Remove the inner logger and rely on the outer one.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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