You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by Alistair Young <al...@smo.uhi.ac.uk> on 2007/03/16 15:41:17 UTC
[AXIS2] targetnamspace wrong in Axis2 version of wsdl with imported xsd
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
Re: [AXIS2] targetnamspace wrong in Axis2 version of wsdl with imported xsd
Posted by Alistair Young <al...@smo.uhi.ac.uk>.
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: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.
>>
>>
>>
>> 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
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>
Re: [AXIS2] targetnamspace wrong in Axis2 version of wsdl with imported xsd
Posted by Amila Suriarachchi <am...@gmail.com>.
Seems to be a problem with the build. Can some one please look into this?
And also can someone please remove the misleading
http://people.apache.org/dist/axis2/nightly/axis2-1.1.1-SNAPSHOT.zip link as
well?
since we do not do any developments in Axis2 1.1.1 branch actually there is
no point in keeping this link.
On 3/20/07, Alistair Young <al...@smo.uhi.ac.uk> wrote:
>
> I tried axis2-SNAPSHOT and got this:
> export AXIS2_HOME=/Users/alistair/apps/axis2-SNAPSHOT-200307
> $AXIS2_HOME/bin/wsdl2java.sh -uri $PWD/wsdl/collectionmanager.wsdl -ss -sd
> -d xmlbeans -xsdconfig $PWD/wsdl/askws.xsdconfig -o $PWD/service -p
> uk.ac.ox.oucs.ask.repo.ws.collectionmanager
> Exception in thread "main" java.lang.NoClassDefFoundError:
> javax/wsdl/WSDLException
>
> Alistair
>
>
> --------------
> mov eax,1
> mov ebx,0
> int 80h
>
>
>
>
> On 20 Mar 2007, at 12:00, Amila Suriarachchi wrote:
>
>
>
> On 3/20/07, Alistair Young <al...@smo.uhi.ac.uk> wrote:
> >
> > I tried the nightly but it doesn't have the xsdconfig support for
> > wsdl2java that is trunk. Is the fix in trunk?
> >
>
> Are you using Axis2 1.1.1-SNAPSHOT or Axis2-SNAPSHOT?
> I am not getting you. it is in trunk. take a build from the trunk.
>
> Alistair
> >
> >
> > --------------
> > mov eax,1
> > mov ebx,0
> > int 80h
> >
> >
> >
> >
> > On 19 Mar 2007, at 10:28, Amila Suriarachchi wrote:
> >
> >
> >
> > 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.xsddoes 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<al...@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.
> >
> >
> >
>
>
> --
> Amila Suriarachchi,
> WSO2 Inc.
>
>
>
--
Amila Suriarachchi,
WSO2 Inc.
Re: [AXIS2] targetnamspace wrong in Axis2 version of wsdl with imported xsd
Posted by Alistair Young <al...@smo.uhi.ac.uk>.
I tried axis2-SNAPSHOT and got this:
export AXIS2_HOME=/Users/alistair/apps/axis2-SNAPSHOT-200307
$AXIS2_HOME/bin/wsdl2java.sh -uri $PWD/wsdl/collectionmanager.wsdl -
ss -sd -d xmlbeans -xsdconfig $PWD/wsdl/askws.xsdconfig -o $PWD/
service -p uk.ac.ox.oucs.ask.repo.ws.collectionmanager
Exception in thread "main" java.lang.NoClassDefFoundError: javax/wsdl/
WSDLException
Alistair
--------------
mov eax,1
mov ebx,0
int 80h
On 20 Mar 2007, at 12:00, Amila Suriarachchi wrote:
>
>
> On 3/20/07, Alistair Young <al...@smo.uhi.ac.uk> wrote:
> I tried the nightly but it doesn't have the xsdconfig support for
> wsdl2java that is trunk. Is the fix in trunk?
>
> Are you using Axis2 1.1.1-SNAPSHOT or Axis2-SNAPSHOT?
> I am not getting you. it is in trunk. take a build from the trunk.
>
> Alistair
>
>
> --------------
> mov eax,1
> mov ebx,0
> int 80h
>
>
>
>
> On 19 Mar 2007, at 10:28, Amila Suriarachchi wrote:
>
>>
>>
>> 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.
>
>
>
>
> --
> Amila Suriarachchi,
> WSO2 Inc.
Re: [AXIS2] targetnamspace wrong in Axis2 version of wsdl with imported xsd
Posted by Amila Suriarachchi <am...@gmail.com>.
On 3/20/07, Alistair Young <al...@smo.uhi.ac.uk> wrote:
>
> I tried the nightly but it doesn't have the xsdconfig support for
> wsdl2java that is trunk. Is the fix in trunk?
>
Are you using Axis2 1.1.1-SNAPSHOT or Axis2-SNAPSHOT?
I am not getting you. it is in trunk. take a build from the trunk.
Alistair
>
>
> --------------
> mov eax,1
> mov ebx,0
> int 80h
>
>
>
>
> On 19 Mar 2007, at 10:28, Amila Suriarachchi wrote:
>
>
>
> On 3/19/07, Alistair Young <al...@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<al...@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.
>
>
>
--
Amila Suriarachchi,
WSO2 Inc.
Re: [AXIS2] targetnamspace wrong in Axis2 version of wsdl with imported xsd
Posted by Alistair Young <al...@smo.uhi.ac.uk>.
I tried the nightly but it doesn't have the xsdconfig support for
wsdl2java that is trunk. Is the fix in trunk?
Alistair
--------------
mov eax,1
mov ebx,0
int 80h
On 19 Mar 2007, at 10:28, Amila Suriarachchi wrote:
>
>
> On 3/19/07, Alistair Young <al...@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.
Re: [AXIS2] targetnamspace wrong in Axis2 version of wsdl with imported xsd
Posted by Amila Suriarachchi <am...@gmail.com>.
On 3/19/07, Alistair Young <al...@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 <al...@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<al...@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.
Re: [AXIS2] targetnamspace wrong in Axis2 version of wsdl with imported xsd
Posted by Alistair Young <al...@smo.uhi.ac.uk>.
> <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
> 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 <al...@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.
Re: [AXIS2] targetnamspace wrong in Axis2 version of wsdl with imported xsd
Posted by Amila Suriarachchi <am...@gmail.com>.
On 3/19/07, Alistair Young <al...@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<al...@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.
Re: [AXIS2] targetnamspace wrong in Axis2 version of wsdl with imported xsd
Posted by Alistair Young <al...@smo.uhi.ac.uk>.
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.
>
>
>
> 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
>
>
>
>
>
>
>
>
>
>
>
>
>
RE: [AXIS2] targetnamspace wrong in Axis2 version of wsdl with imported xsd
Posted by Kin Onn Low <ko...@ap.savi.com>.
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.
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
Re: [AXIS2] targetnamspace wrong in Axis2 version of wsdl with imported xsd
Posted by Alistair Young <al...@smo.uhi.ac.uk>.
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
>
>
>
>