Return-Path: Delivered-To: apmail-ws-axis-user-archive@www.apache.org Received: (qmail 12470 invoked from network); 19 Mar 2007 10:29:09 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 19 Mar 2007 10:29:09 -0000 Received: (qmail 68019 invoked by uid 500); 19 Mar 2007 10:29:07 -0000 Delivered-To: apmail-ws-axis-user-archive@ws.apache.org Received: (qmail 68003 invoked by uid 500); 19 Mar 2007 10:29:07 -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 67992 invoked by uid 99); 19 Mar 2007 10:29:07 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 19 Mar 2007 03:29:07 -0700 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 (herse.apache.org: domain of amilasuriarachchi@gmail.com designates 64.233.182.191 as permitted sender) Received: from [64.233.182.191] (HELO nf-out-0910.google.com) (64.233.182.191) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 19 Mar 2007 03:28:57 -0700 Received: by nf-out-0910.google.com with SMTP id o63so937071nfa for ; Mon, 19 Mar 2007 03:28:36 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=qCx9GPSgwLArr//Owpmc4ce8C9rb+uJ5eB847Nn/X7N9rBF4JYxfsaWO6DmP3UEfvbgEq5PirFPPmsAB63jpjJy+Mi/c1JjRLi5dm0SebGNrRRBCqpI/sw+RGLwLw1e/J/OT3S8KnIOdoAeWuFLXNp4kCmESEwOPRSXfLv+9uPg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=HW4oC8TQ8lR96ftsrxgqKDx/pSNFioRDK4yUztXqt3WAOPyXh58dtZZmff5aaAgPi+22ndl65/HClvJuqT71oP4Hu86e7Qi1rRuflq32CxK202UEqzJzltZvgy8Z5il2NYG/O2UIBwsdp3K1zI32JK8w6pHi6gb6GEuo9+HWuvw= Received: by 10.82.162.14 with SMTP id k14mr9744918bue.1174300116292; Mon, 19 Mar 2007 03:28:36 -0700 (PDT) Received: by 10.82.178.14 with HTTP; Mon, 19 Mar 2007 03:28:36 -0700 (PDT) Message-ID: <60708f4b0703190328l47cf59a9le33d6e23a2602602@mail.gmail.com> Date: Mon, 19 Mar 2007 15:58:36 +0530 From: "Amila Suriarachchi" To: axis-user@ws.apache.org Subject: Re: [AXIS2] targetnamspace wrong in Axis2 version of wsdl with imported xsd In-Reply-To: <0088B0DD-38F9-4241-BA48-A915ABE57B65@smo.uhi.ac.uk> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_66958_16651665.1174300116243" References: <264F3EC3-3C9D-41BC-80A7-54473F78CD1B@smo.uhi.ac.uk> <60708f4b0703190249r356c5ba8lc1d7700a95ca1f89@mail.gmail.com> <0088B0DD-38F9-4241-BA48-A915ABE57B65@smo.uhi.ac.uk> X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_66958_16651665.1174300116243 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline On 3/19/07, Alistair Young wrote: > > schemaLocation=" ask-repo-types.xsd"/> > > I'm using trunk from about 2 weeks ago. I can only use trunk as I need the > xsdconfig support, which isn't in 1.1.1. The xsd and wsdl are in the same > directory. > > But those generated xsd files must contain all the namespaces as in the > original xsd > > they do - but the generated xsd has a different name from the original so > the original wsdl will never work > you mean wsdl file still contain the old (original xsd file name?) In that case please check with a new build I fixed this issue Does your service name map with the wsdl name? > > yes > > document/literal type wsdl > > my wsdl is doc-lit anyway > > thanks, > > Alistair > > > -------------- > mov eax,1 > mov ebx,0 > int 80h > > > > > On 19 Mar 2007, at 09:49, Amila Suriarachchi wrote: > > > On 3/19/07, Alistair Young wrote: > > > > that will never work as the imported namespace is renamed by Axis2: > > original WSDL: > > > schemaLocation=" ask-repo-types.xsd"/> > > > > ask-repo-types.xsd is renamed to xsd0.xsd, so ask-repo-types.xsd does > > not exist in the deployed service. > > > > the generated wsdl bears no resemblence to the original - why does axis2 > > do that? > > > > Alistair > > > > > > -------------- > > mov eax,1 > > mov ebx,0 > > int 80h > > > > > > > > > > On 19 Mar 2007, at 08:56, Kin Onn Low wrote: > > > > To user your user defined wsdl, add : > > > > > > true > > > > > > to the services.xml file. > > > > ------------------------------ > > > > * From:* Alistair Young [ mailto:alistair@smo.uhi.ac.uk] > > > > * Sent:* Monday, March 19, 2007 4:45 PM > > * To:* axis-user@ws.apache.org > > * Subject:* Re: [AXIS2] targetnamspace wrong in Axis2 version of wsdl > > with imported xsd > > > > > > Can Axis2 wsdl2java not handle imported schema files? The imported xsd > > file gets renamed to xsd0.xsd and all the namespaces in it are ignored. > > xsd0.xsd is not referenced in the new wsdl - why is it creating a NEW > > wsdl? and all the types that reference xsd0.xsd get changed to > > xsi:anyType, so nothing works. > > > > > Are you working with the Axis2 1.1.1 or nightly builds? > those file names are re named since there is a problem if there is a > location specifed other than the same location ( I.e eg > ../../test/test.xsd). But those generated xsd files must contain all the > namespaces as in the original xsd. (please log a jira for this). this > generated xsd file syntactically must be equal to original. > Does your service name map with the wsdl name? otherwise it does not pick > the wsdl. > In Axis2 1.1.1 a given wsdl is always converted to document/literal type > wsdl. But it is fixed now. > > > > > > -- > Amila Suriarachchi, > WSO2 Inc. > > > -- Amila Suriarachchi, WSO2 Inc. ------=_Part_66958_16651665.1174300116243 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline

On 3/19/07, Alistair Young <alistair@smo.uhi.ac.uk> wrote:
<xs:import id="askRepoTypes" namespace="uk:ac:ox:oucs:ask:repo:ws:types" schemaLocation=" ask-repo-types.xsd"/>
 I'm using trunk from about 2 weeks ago. I can only use trunk as I need the xsdconfig support, which isn't in 1.1.1. The xsd and wsdl are in the same directory.

 But those generated xsd files must contain all the namespaces as in the original xsd
they do - but the generated xsd has a different name from the original so the original wsdl will never work

you mean wsdl file still contain the old (original xsd file name?)
In that case please check with a new build I fixed this issue


 

Does your service name map with the wsdl name? 
yes

document/literal type wsdl
my wsdl is doc-lit anyway

thanks,

Alistair


--------------
mov eax,1
mov ebx,0
int 80h

On 19 Mar 2007, at 09:49, Amila Suriarachchi wrote:


On 3/19/07, Alistair Young < alistair@smo.uhi.ac.uk> wrote:
that will never work as the imported namespace is renamed by Axis2:

original WSDL:
<xs:import id="askRepoTypes" namespace="uk:ac:ox:oucs:ask:repo:ws:types" schemaLocation=" ask-repo-types.xsd"/>

ask-repo-types.xsd is renamed to xsd0.xsd, so ask-repo-types.xsd does not exist in the deployed service.

the generated wsdl bears no resemblence to the original - why does axis2 do that?

Alistair


--------------
mov eax,1
mov ebx,0
int 80h

On 19 Mar 2007, at 08:56, Kin Onn Low wrote:

To user your user defined wsdl, add :

 

<parameter name="useOriginalwsdl">true</parameter>

 

to the services.xml  file.

 

From: Alistair Young [ mailto:alistair@smo.uhi.ac.uk]
Sent: Monday, March 19, 2007 4:45 PM
To: axis-user@ws.apache.org
Subject: Re: [AXIS2] targetnamspace wrong in Axis2 version of wsdl with imported xsd

 

Can Axis2 wsdl2java not handle imported schema files? The imported xsd file gets renamed to xsd0.xsd and all the namespaces in it are ignored. xsd0.xsd is not referenced in the new wsdl - why is it creating a NEW wsdl? and all the types that reference  xsd0.xsd get changed to xsi:anyType, so nothing works.


Are you working with the  Axis2 1.1.1 or nightly builds?
those file names are re named since there is a problem if there is a location specifed other than the same location ( I.e eg ../../test/test.xsd). But those generated xsd files must contain all the namespaces as in the original xsd. (please log a jira for this). this generated xsd file syntactically must be equal to original.
Does your service name map with the wsdl name? otherwise it does not pick the wsdl.
In Axis2 1.1.1 a given wsdl is always converted to document/literal type wsdl. But it is fixed now.





--
Amila Suriarachchi,
WSO2 Inc.




--
Amila Suriarachchi,
WSO2 Inc. ------=_Part_66958_16651665.1174300116243--