Return-Path: Delivered-To: apmail-ws-axis-c-dev-archive@www.apache.org Received: (qmail 55554 invoked from network); 1 Jul 2005 04:06:02 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 1 Jul 2005 04:06:02 -0000 Received: (qmail 5806 invoked by uid 500); 1 Jul 2005 04:06:02 -0000 Delivered-To: apmail-ws-axis-c-dev-archive@ws.apache.org Received: (qmail 5775 invoked by uid 500); 1 Jul 2005 04:06:01 -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 5696 invoked by uid 99); 1 Jul 2005 04:06:01 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [192.87.106.226] (HELO ajax.apache.org) (192.87.106.226) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 30 Jun 2005 21:06:00 -0700 Received: from ajax.apache.org (ajax.apache.org [127.0.0.1]) by ajax.apache.org (Postfix) with ESMTP id D688815 for ; Fri, 1 Jul 2005 06:05:57 +0200 (CEST) Message-ID: <367879238.1120190757876.JavaMail.jira@ajax.apache.org> Date: Fri, 1 Jul 2005 06:05:57 +0200 (CEST) From: "Dushshantha Chandradasa (JIRA)" To: axis-c-dev@ws.apache.org Subject: [jira] Commented: (AXISCPP-722) Overloaded processException in AxisEngineException class In-Reply-To: <32668418.1120190757050.JavaMail.jira@ajax.apache.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N [ http://issues.apache.org/jira/browse/AXISCPP-722?page=comments#action_12314847 ] Dushshantha Chandradasa commented on AXISCPP-722: ------------------------------------------------- On Thu, 2005-06-30 at 10:16, John Hawkins wrote: > I've always questioned why we have processException in the first place > ! I've never understood why you would want it. If the same fault is > thrown by different processes then you would have to know which > process call you were in to do anything useful. I have no idea why we > don't just remove it. I think you should always handle exceptions in > the calling program using try catch as usual. > Overloaded processException in AxisEngineException class > -------------------------------------------------------- > > Key: AXISCPP-722 > URL: http://issues.apache.org/jira/browse/AXISCPP-722 > Project: Axis-C++ > Type: Bug > Components: Server - Engine > Versions: current (nightly) > Environment: All > Reporter: Dushshantha Chandradasa > > Samisa Abeysinghe wrote on 30/06/2005 > > 11:04:29: > > > > > Hi All, > > > We have several overloaded forms of processException in > > > AxisEngineException class. > > > > > > I am sure that we are not using all of those. It is quite hard > > to > > > undestand and locate the problem locations when maintaining the > > > implementation. Shall we drop those that are not used from the list > > > below? > > > > > > void processException(const exception* e); > > > void processException(const exception* e, const int > > iExceptionCode); > > > void processException (const exception* e, char* pcMessage); > > > void processException(const int iExceptionCode); > > > void processException(const int iExceptionCode, char* > > pcMessage); > > > > > > BTW, some can be replaced with the copy constructor. I think we > > > can drop the top 3 and keep the bottom 2. Sometime it is better to > > > KISS ;-) > > > > > > Thanks, > > > Samisa... -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira