Return-Path: Delivered-To: apmail-ws-axis-user-archive@www.apache.org Received: (qmail 89971 invoked from network); 22 Dec 2007 05:28:25 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 22 Dec 2007 05:28:25 -0000 Received: (qmail 79441 invoked by uid 500); 22 Dec 2007 05:28:06 -0000 Delivered-To: apmail-ws-axis-user-archive@ws.apache.org Received: (qmail 79429 invoked by uid 500); 22 Dec 2007 05:28:06 -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 79418 invoked by uid 99); 22 Dec 2007 05:28:06 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 21 Dec 2007 21:28:06 -0800 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of keithgchapman@gmail.com designates 72.14.246.249 as permitted sender) Received: from [72.14.246.249] (HELO ag-out-0708.google.com) (72.14.246.249) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 22 Dec 2007 05:27:43 +0000 Received: by ag-out-0708.google.com with SMTP id 26so2883976agb.5 for ; Fri, 21 Dec 2007 21:27:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; bh=BBal7SpP6KG45jMHwqIzc75xzEIY9rghY6br2QVF2Do=; b=ARsfHRhhHEPQ2suyiaUb8PzrMM+EAm7YoB933wNiqBKFrmzpMQaCjsUdcmlVeTAW2W1X6JX9v+mW4xo4iN4+3D3UNrFMyBdPpwbvaGA8nZgTXbEVrGzxLt5PtGKT/EQVhjn8/E5D3p1KN9mDVi2mSVsfx0AMcg9h3fiK9zO4I1I= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=KNPy3+ha91wQJZ73Sgtwt5OJHdK4mcTBR3a+amYBCRGVTQatuzu1pUfj8/5kdzNkZ87/WfYpo12yyePVKxuoRDX0HI9ZvuWi7eW0shsoXmNpYIML5VvUFm3zZNfJQMKlnwj4E55NJjgY30YYPgbRGFMmV6csUNWACfaDB0ZAHxk= Received: by 10.100.251.5 with SMTP id y5mr4311652anh.12.1198301265467; Fri, 21 Dec 2007 21:27:45 -0800 (PST) Received: by 10.70.9.12 with HTTP; Fri, 21 Dec 2007 21:27:45 -0800 (PST) Message-ID: Date: Sat, 22 Dec 2007 10:57:45 +0530 From: "keith chapman" To: axis-user@ws.apache.org Subject: Re: [Axis2] Service name change - creates WSDL generation problem. In-Reply-To: <200712191533.46277.p.d.hargreaves@bedsearcher.co.uk> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_1654_18526376.1198301265456" References: <200712191533.46277.p.d.hargreaves@bedsearcher.co.uk> X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_1654_18526376.1198301265456 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline If there is a WSDL inside your META-INF and you want to use that WSDL then the servicename in the services.xml should match the servicename in the WSDL. If it does not match Axis2 ignores the WSDL and creates the service using the services.xml. If you rename the service in the WSDL things should work for you. Thanks, Keith. On Dec 19, 2007 9:03 PM, Peter Hargreaves wrote: > I may have done my renaming wrongly, or missed a trick. > > I have successfully developed and tested a service using Axis2 based on > generation from our own wsdl. > > For depolyment we needed to change the service name. To do this I: > > 1) Took a copy of the service.xml file generated from our wsdl. > 2) Renamed the tag inside service.xml then used > it to > generate compile and jar the webservice. > 3) Then changed oldname.aar to newname.aar > 4) Run our JUnit tests on the new service successfully. > > However, when we request newname?wsdl the returned wsdl is faulty. > > Our original wsdl imported multiple files to define the schema: > > > > schemaLocation="BsSearchEstabsRQ.xsd"/> > > ... > > > When requested from the running service they became: > > > elementFormDefault="unqualified"> > schemaLocation="oldname?xsd=xsd0"/> > > ... > > > This was fine, but when requested from the renamed service they become: > > > elementFormDefault="qualified" > targetNamespace="http://server.service.bs.org"> > > > > type="xs:anyType"/> > > > > > ... > > > The import references are missing and the complexTypes generated in their > place bear no resemblance. > > Have I done my renaming wrongly, have I missed a trick, or is there a bug? > Any > comments or advice would be welcome. > > Many thanks, > Pete.H. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org > For additional commands, e-mail: axis-user-help@ws.apache.org > > -- Keith Chapman WSO2 Inc. Oxygen for Web Services Developers. http://wso2.org/ ------=_Part_1654_18526376.1198301265456 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline If there is a WSDL inside your META-INF and you want to use that WSDL then the servicename in the services.xml should match the servicename in the WSDL. If it does not match Axis2 ignores the WSDL and creates the service using the services.xml. If you rename the service in the WSDL things should work for you.

Thanks,
Keith.

On Dec 19, 2007 9:03 PM, Peter Hargreaves < p.d.hargreaves@bedsearcher.co.uk> wrote:
I may have done my renaming wrongly, or missed a trick.

I have successfully developed and tested a service using Axis2 based on
generation from our own wsdl.

For depolyment we needed to change the service name. To do this I:

1) Took a copy of the service.xml file generated from our wsdl.
2) Renamed the <service name="newname"> tag inside service.xml then used it to
generate compile and jar the webservice.
3) Then changed oldname.aar to newname.aar
4) Run our JUnit tests on the new service successfully.

However, when we request newname?wsdl the returned wsdl is faulty.

Our original wsdl imported multiple files to define the schema:

<wsdl:types>
 <xs:schema>
   <xs:import namespace="http://www.ournamespace"
schemaLocation="BsSearchEstabsRQ.xsd"/>
 </xs:schema>
  ...
<wsdl:types>

When requested from the running service they became:

<wsdl:types>
 <xs:schema attributeFormDefault="unqualified"
elementFormDefault="unqualified">
   <xs:import namespace="http://www.ournamespace"
schemaLocation="oldname?xsd=xsd0"/>
 </xs:schema>
  ...
<wsdl:types>

This was fine, but when requested from the renamed service they become:

<wsdl:types>
 <xs:schema attributeFormDefault="qualified" elementFormDefault="qualified"
targetNamespace=" http://server.service.bs.org">
  <xs:element name="searchEstabs">
    <xs:complexType>
      <xs:sequence>
        <xs:element minOccurs="0" name="searchEstabs" nillable="true"
type="xs:anyType"/>
      </xs:sequence>
    </xs:complexType>
  </xs:element>
 </xs:schema>
  ...
</wsdl:types>

The import references are missing and the complexTypes generated in their
place bear no resemblance.

Have I done my renaming wrongly, have I missed a trick, or is there a bug? Any
comments or advice would be welcome.

Many thanks,
Pete.H.

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org




--
Keith Chapman
WSO2 Inc.
Oxygen for Web Services Developers.
http://wso2.org/ ------=_Part_1654_18526376.1198301265456--