Return-Path: Delivered-To: apmail-ws-axis-c-dev-archive@www.apache.org Received: (qmail 89467 invoked from network); 4 Oct 2004 05:11:45 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 4 Oct 2004 05:11:45 -0000 Received: (qmail 27600 invoked by uid 500); 4 Oct 2004 05:09:40 -0000 Delivered-To: apmail-ws-axis-c-dev-archive@ws.apache.org Received: (qmail 27555 invoked by uid 500); 4 Oct 2004 05:09:39 -0000 Mailing-List: contact axis-c-dev-help@ws.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: List-Id: "Apache AXIS C Developers List" Reply-To: "Apache AXIS C Developers List" Delivered-To: mailing list axis-c-dev@ws.apache.org Received: (qmail 27492 invoked by uid 99); 4 Oct 2004 05:09:38 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=NO_REAL_NAME X-Spam-Check-By: apache.org Received: from [192.18.33.10] (HELO exchange.sun.com) (192.18.33.10) by apache.org (qpsmtpd/0.28) with SMTP; Sun, 03 Oct 2004 22:09:38 -0700 Received: (qmail 8109 invoked from network); 4 Oct 2004 05:11:32 -0000 Received: from localhost (HELO nagoya) (127.0.0.1) by nagoya.betaversion.org with SMTP; 4 Oct 2004 05:11:32 -0000 Message-ID: <2142147094.1096866692159.JavaMail.apache@nagoya> Date: Sun, 3 Oct 2004 22:11:32 -0700 (PDT) From: axis-c-dev@ws.apache.org To: axis-c-dev@ws.apache.org Subject: [jira] Commented: (AXISCPP-172) Remove _DEBUG flag use In-Reply-To: <2057193853.1096375471909.JavaMail.apache@nagoya> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N The following comment has been added to this issue: Author: sanjaya singharage Created: Sun, 3 Oct 2004 10:10 PM Body: At 1.3 beta stage there is a compilation issue on windows that is preventing the use of ENABLE_AXISTRACE macro. Please refer to bug number 162 for details. Fixing of this bug may require some API changes in the transport library, which I think is better done in the next release. --------------------------------------------------------------------- View this comment: http://issues.apache.org/jira/browse/AXISCPP-172?page=comments#action_53653 --------------------------------------------------------------------- View the issue: http://issues.apache.org/jira/browse/AXISCPP-172 Here is an overview of the issue: --------------------------------------------------------------------- Key: AXISCPP-172 Summary: Remove _DEBUG flag use Type: Improvement Status: Unassigned Priority: Minor Project: Axis-C++ Fix Fors: 1.3 Beta Versions: 1.3 Beta Assignee: Reporter: John Hawkins Created: Tue, 28 Sep 2004 5:44 AM Updated: Sun, 3 Oct 2004 10:10 PM Due: Wed, 25 Nov 2009 12:00 AM Description: Currently the code uses both the _DEBUG and ENABLE_AXISTRACE to utilise trace. We should replace any flags that are not ENABLE_AXISTRACE. NOTE: Trace is for developers only when they are trying to debug any problems that occur on someone elses system ie when they are a true "user" and we cannot attach a debugger we can ask them to turn trace on and we can analyse the output. --------------------------------------------------------------------- JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira