removing the import and embedding the schema directly in the wsdl
types solves the problem. Looks like wsdl2java can't handle imported
schema.
Alistair
--------------
mov eax,1
mov ebx,0
int 80h
On 19 Mar 2007, at 08:57, Alistair Young 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:[EMAIL PROTECTED]
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.
thanks,
Alistair
--------------
mov eax,1
mov ebx,0
int 80h
On 16 Mar 2007, at 14:41, Alistair Young wrote:
in META-INF/TestService.wsdl:
targetNamespace="uk:ac:ox:oucs:ask:repo:ws:collectionmanager"
xmlns:rt="uk:ac:ox:oucs:ask:repo:ws:types"
axis2-admin listing the service:
targetNamespace="http://collectionmanager.ws.repo.ask.oucs.ox.ac.uk";
and xmlns:rt has been removed
xmlns:rt has been imported from an external xsd into the wsdl
all these changes cause the service to break.
How can I stop Axis2 rewriting the wsdl?
thanks,
Alistair
--------------
mov eax,1
mov ebx,0
int 80h
