Return-Path: Delivered-To: apmail-ws-axis-dev-archive@www.apache.org Received: (qmail 58354 invoked from network); 11 May 2004 05:55:02 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 11 May 2004 05:55:02 -0000 Received: (qmail 10076 invoked by uid 500); 11 May 2004 05:55:48 -0000 Delivered-To: apmail-ws-axis-dev-archive@ws.apache.org Received: (qmail 9814 invoked by uid 500); 11 May 2004 05:55:45 -0000 Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-dev@ws.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list axis-dev@ws.apache.org Received: (qmail 9804 invoked by uid 98); 11 May 2004 05:55:45 -0000 Received: from iasandcb@tmax.co.kr by hermes.apache.org by uid 82 with qmail-scanner-1.20 (clamuko: 0.70. Clear:RC:0(216.71.84.236):. Processed in 0.05145 secs); 11 May 2004 05:55:45 -0000 X-Qmail-Scanner-Mail-From: iasandcb@tmax.co.kr via hermes.apache.org X-Qmail-Scanner: 1.20 (Clear:RC:0(216.71.84.236):. Processed in 0.05145 secs) Received: from unknown (HELO kiku.7777.net) (216.71.84.236) by hermes.apache.org with SMTP; 11 May 2004 05:55:45 -0000 Received: from ias ([210.216.114.99]) by kiku.7777.net (8.11.6/8.11.6) with ESMTP id i4B5sjF06643 for ; Tue, 11 May 2004 14:54:46 +0900 Message-Id: <200405110554.i4B5sjF06643@kiku.7777.net> From: "Ias" To: Subject: RE: About JAX-RPC 1.1 compliance of JAXRPCException and ServiceException Date: Tue, 11 May 2004 14:54:43 +0900 MIME-Version: 1.0 Content-Type: text/plain; charset="ks_c_5601-1987" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 Thread-Index: AcQ3GOPEj/U3jbRaRmSmEZ8zA8MLjgAArwYg In-Reply-To: <200405110529.i4B5TE601475@kiku.7777.net> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 X-Spam-Rating: hermes.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Jongjin and I discussed this issue, particularly, printing stack trace of the cause from runtime exceptions for JAX-RPC. Jongjin said Sun's JAX-RPC 1. 1 RI actually dumps stack trace of the cause gracefully, and we agree that it's not due to overriding printStackTrace methods but using some logger for the job. Probably this approach also can help Axis to improve server- side exception display. Regards, Ias ========================================================= Lee, Changshin (Korean name) Ias (International name) Company Web Site: http://www.tmax.co.kr Personal Web Site: http://www.iasandcb.pe.kr --------------------------------------------------------- JSR 201, 204, 222 and 224 Expert Group Member Apache Web Services Project Member R&D Center Tmax Soft, Inc. ========================================================= > -----Original Message----- > From: Ias [mailto:iasandcb@tmax.co.kr] > Sent: Tuesday, May 11, 2004 2:29 PM > To: axis-dev@ws.apache.org > Subject: About JAX-RPC 1.1 compliance of JAXRPCException and > ServiceException > > I found that commits recorded at http://marc.theaimsgroup.com/?l=axis- > dev&m=108422347730988&w=2 caused incompliance of JAX-RPC 1.1 > APIs described at > http://java.sun.com/webservices/docs/1.3/api/index.html while > I was working on JAX-RPC 1.1 TCK signature test. I'd like to > recommend paying as much attention as possible to the > standard API set when handling > javax.xml.* packages. > > By the way, which do you think is better for resolving this > problem, rollback or commit changes of removing the > incompatible methods? > > Thanks, > > Ias > > ========================================================= > Lee, Changshin (Korean name) > Ias (International name) > Company Web Site: http://www.tmax.co.kr > Personal Web Site: http://www.iasandcb.pe.kr > --------------------------------------------------------- > JSR 201, 204, 222 and 224 Expert Group Member Apache Web > Services Project Member R&D Center Tmax Soft, Inc. > ========================================================= >