Return-Path: Delivered-To: apmail-ws-axis-user-archive@www.apache.org Received: (qmail 24645 invoked from network); 2 Feb 2004 08:39:14 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 2 Feb 2004 08:39:14 -0000 Received: (qmail 21555 invoked by uid 500); 2 Feb 2004 08:38:28 -0000 Delivered-To: apmail-ws-axis-user-archive@ws.apache.org Received: (qmail 21534 invoked by uid 500); 2 Feb 2004 08:38:28 -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: Delivered-To: mailing list axis-user@ws.apache.org Received: (qmail 21505 invoked from network); 2 Feb 2004 08:38:28 -0000 Received: from unknown (HELO smtp.inet.fi) (192.89.123.192) by daedalus.apache.org with SMTP; 2 Feb 2004 08:38:28 -0000 Received: from blis-project.org (unknown [193.211.37.35]) by smtp.inet.fi (Postfix) with ESMTP id 1C3B33C1D8 for ; Mon, 2 Feb 2004 10:38:40 +0200 (EET) Message-ID: <401E0C6B.2090308@blis-project.org> Date: Mon, 02 Feb 2004 10:38:03 +0200 From: "BLIS Webmaster (Patrick Houbaux)" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: axis-user@ws.apache.org Subject: Re: Potential bugs in Axis 1.2 alpha (java): java.lang.String mapping References: <4018CB87.1090509@blis-project.org> In-Reply-To: <4018CB87.1090509@blis-project.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Hi all, Anybody has any thoughts/ideas about that problem? Regards, Patrick. BLIS Webmaster (Patrick Houbaux) wrote: > Hi all, > > I made a small experience that could lead to some potential bugs in Axis > 1.2 alpha. > I will try to explain it clearly ;) > > 1- I used Axis 1.2 alpha to expose my webservice (server side) > > 2- On the client side (using Axis 1.1), I noticed that I could not > generate the client stub anymore for my webservice, the message was: > > ====================== > generate_stub_MyServide.RPC: > WSDL2Java http://localhost:8080/axis/services/MyServide.RPC?wsdl > Parsing XML file: http://localhost:8080/axis/services/MyServide.RPC?wsdl > java.io.IOException: Type > {http://www.w3.org/2003/05/soap-encoding}string is referenced but not > defined. > BUILD SUCCESSFUL > Total time: 2 seconds ====================== > > 3- Then I started to wonder why, so I tried to use Axis 1.2 alpha in my > client as well and suddently the client stub generation was working. > > 4- Then I analysed the difference between the WSDL generated with Axis > 1.2 alpha and Axis 1.1 and I noticed a difference in the mapping of the > "java.lang.String" type. > > For instance: > ============ portion of the WSDL generated with AXIS 1.1 ============ > > > > > > > ===================================================================== > > ============ portion of the WSDL generated with AXIS 1.2 alpha ============ > > > > > > > ===================================================================== > > So the questions are : a) Why doesn't Axis 1.2 alpha (java2wsdl) map the > type "java.lang.String" to "xsd:string" anymore like it used to be in > Axis 1.1? > Is this a bug? > > b) Why does Axis 1.2 alpha (wsdl2java) understand "tns2:string" and map > it correctly to "java.lang.String" during the client stub generation? > Is this a second bug? > > c) Am I doing something wrong somewhere? > > Cheers, > Patrick.