Return-Path: Delivered-To: apmail-ws-axis-user-archive@www.apache.org Received: (qmail 72156 invoked from network); 5 Jun 2007 17:23:01 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 5 Jun 2007 17:23:01 -0000 Received: (qmail 94700 invoked by uid 500); 5 Jun 2007 17:22:58 -0000 Delivered-To: apmail-ws-axis-user-archive@ws.apache.org Received: (qmail 93699 invoked by uid 500); 5 Jun 2007 17:22:55 -0000 Mailing-List: contact axis-user-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-user@ws.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list axis-user@ws.apache.org Received: (qmail 93688 invoked by uid 99); 5 Jun 2007 17:22:55 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 Jun 2007 10:22:55 -0700 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_HELO_PASS,UNPARSEABLE_RELAY X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of scd@metafile.com designates 65.123.219.140 as permitted sender) Received: from [65.123.219.140] (HELO metafile.com) (65.123.219.140) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 Jun 2007 10:22:50 -0700 DKIM-Signature: a=rsa-sha1; c=simple; d=metafile.com; s=Metafile; l=10558; t=1181064151; x=1181668951; q=dns; h=Received:From:To: Subject:Date:Message-ID:MIME-Version:Content-Type:Thread-Index: Reply-To; b=X/tMweoGQNi3js1TST4BGyjrKRt0jx6ECoVtUPREbcA7QcPvKGBt dqtkPGQruWXJsjpEudg8KgCAOPRWhLw1fUt/9kD7koYH1UWsP2nL+kUcQuY1yOcH ATWiKtQPePpnaze2Hb0xGWdMwiHximJD67T5vrWAw27oVaaf+u3BpK0= Received: from SCD9600 by metafile.com (MDaemon PRO v9.5.6) with ESMTP id 53-md50000020887.msg for ; Tue, 05 Jun 2007 12:22:29 -0500 From: "Shawn Dever" To: Subject: AXIS 2 WSDL2Java Oddly Naming Exceptions Date: Tue, 5 Jun 2007 12:22:26 -0500 Message-ID: <001d01c7a796$16847160$460210ac@metafile.lan> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_001E_01C7A76C.2DAE6960" X-Mailer: Microsoft Office Outlook 11 Thread-Index: AcenlhY69qLL6fqmTEuO8TYit0K55Q== X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028 X-Authenticated-Sender: scd@metafile.com X-Spam-Processed: metafile.com, Tue, 05 Jun 2007 12:22:29 -0500 (not processed: message from valid local sender) X-MDRemoteIP: 172.16.2.70 X-Return-Path: scd@metafile.com X-Envelope-From: scd@metafile.com X-MDaemon-Deliver-To: axis-user@ws.apache.org Reply-To: scd@metafile.com X-MDAV-Processed: metafile.com, Tue, 05 Jun 2007 12:22:31 -0500 X-SPAM-Msg-ID: c:\mdaemon\queues\remote\md35000395663.msg X-SPAM-Msg-License-ID: xjga6ixx X-SPAM-Msg-Sniffer-Results: 0 X-Virus-Checked: Checked by ClamAV on apache.org ------=_NextPart_000_001E_01C7A76C.2DAE6960 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit In hopes that someone might be able shed some light on it, we have reduced our problem to a simple test case. SCENARIO We have a web service with two methods: "Method1" and "Method2". Each method can throw an exception called "CustomException". We use the WSDL2Java to build our Java client proxy. The exception is generated with a name such as "Method1_CustomException". In the client proxy code, both methods now throw/catch "Method1_CustomException". (Notice how the "Method1" is used in the name of the exception.) PROBLEM When the web service designer adds a new method, say "Method3", and we regenerate the client proxy, the exception names changes to "Method3_CustomException". This forces us to modify our existing client code to recognize the name change to the exception. QUESTIONS Is there a way around this problem? Is there a way to force the WSDL2Java to not put the method name in the exception fault? Has anyone experience this issue before (or maybe it is just us). MORE INFORMATION We are using the latest Axis 2 code. The web service is written using Microsoft .NET WCF/Indigo. .Net clients are working fine. We tried WSDL2Java on the WCF Interop Endpoints (see URL below) and the proxy code looks like it will suffer the same problem. http://131.107.72.15/SoapWsdl_Faults_DocLitW_Service_Indigo/AppFaultsService .svc?wsdl In our test web service, we created a method called AAAAExceptions that threw all the exceptions. We thought that by doing this, all the proxy exceptions would be named with this method's name such as: AAAAException_CustomException. Oddly enough, this worked for all but one of the exceptions. Thanks for any guidance you can provide. Shawn ------=_NextPart_000_001E_01C7A76C.2DAE6960 Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable

In hopes that = someone might be able shed some light on it, we have reduced our problem to a simple = test case.

 

SCENARIO =

We have a web = service with two methods: “Method1” and = “Method2”.

Each method can = throw an exception called = “CustomException”.

 

We use the = WSDL2Java to build our Java client proxy.

The exception is = generated with a name such as “Method1_CustomException”.  In the = client proxy code, both methods now throw/catch “Method1_CustomException”.  (Notice how the “Method1” is used in the name of the = exception.)

 

PROBLEM

When the web = service designer adds a new method, say “Method3”, and we regenerate = the client proxy, the exception names changes to “Method3_CustomException”.  This forces us to modify = our existing client code to recognize the name change to the = exception.

 

QUESTIONS

Is there a way = around this problem?

Is there a way to = force the WSDL2Java to not put the method name in the exception = fault?

Has anyone = experience this issue before (or maybe it is just us).

 

MORE = INFORMATION

We are using the = latest Axis 2 code.

The web service is = written using Microsoft .NET WCF/Indigo. 

.Net clients are = working fine.

 

We tried WSDL2Java = on the WCF Interop Endpoints (see URL below) and the proxy code looks like it = will suffer the same problem.  http://131.107.72.15/SoapWsdl_Faults_DocLitW_Servic= e_Indigo/AppFaultsService.svc?wsdl

 

In our test web = service, we created a method called AAAAExceptions that threw all the = exceptions.  We thought that by doing this, all the proxy exceptions would be named with = this method’s name such as: AAAAException_CustomException.  Oddly = enough, this worked for all but one of the = exceptions.

 

Thanks for any = guidance you can provide.

Shawn

 

------=_NextPart_000_001E_01C7A76C.2DAE6960--