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 vasantha sriram <st...@yahoo.com> on 2005/07/31 22:50:09 UTC

classes not generated for the types defined in schema

Please note that the namespace in the wsdl file is a
url.

It generated the service, bindingimpl, stub, locator,
porttype, deploy.wsdd and undeploy.wsdd.
It did not create the java classes that correspond the
types that are referred by the wsdl  ( which are in a
separate schema definition files).

In the stub class, there is a method like this
net.groove.webservices.Groove._2_0.Accounts.AccountList
read(

You can see that AccountList is a type defined int the
schema, but there is no corresponding java file.

Your help is appreciated.

Do I have to copy the types defined in the schema to
the wdsl file ?
Do I have to generate the java classes for the types
separately ?

This is what I see in the console

{http://webservices.groove.net/Groove/2.0/Core/}GrooveRequestHeader
already exis
ts
{http://webservices.groove.net/Groove/2.0/Core/}>GrooveRequestHeader
already exi
sts
{http://webservices.groove.net/Groove/2.0/Core/}GrooveResponseHeader
already exi
sts
{http://webservices.groove.net/Groove/2.0/Core/}>GrooveResponseHeader
already ex
ists
{http://webservices.groove.net/Groove/2.0/Core/}URIList
already exists
{http://webservices.groove.net/Groove/2.0/Core/}IDList
already exists


Thanks


		
____________________________________________________
Start your day with Yahoo! - make it your home page 
http://www.yahoo.com/r/hs 
 

Re: classes not generated for the types defined in schema

Posted by James Wilson <wi...@ociweb.com>.
I had the same problem when I moved the schema into it's own file.  It is now
imported into the wsdl.  If you are using the ant wsdl2java task, I think the
step I took to get the imported schema to generate to java was to add the
mapping child element.  I've pasted below the task call from my build.xml


<wsdl2java url="${wsdl.file}" output="${ws.src.dir}" deployscope="application"
serverside="true" noimports="no" verbose="yes" testcase="no">
<mapping namespace="${ws.namespace}" package="${ws.package}" />
			<mapping namespace="${ws.q.namespace}" package="${ws.q.package}" />
		</wsdl2java>


Quoting vasantha sriram <st...@yahoo.com>:

> Please note that the namespace in the wsdl file is a
> url.
>
> It generated the service, bindingimpl, stub, locator,
> porttype, deploy.wsdd and undeploy.wsdd.
> It did not create the java classes that correspond the
> types that are referred by the wsdl  ( which are in a
> separate schema definition files).
>
> In the stub class, there is a method like this
> net.groove.webservices.Groove._2_0.Accounts.AccountList
> read(
>
> You can see that AccountList is a type defined int the
> schema, but there is no corresponding java file.
>
> Your help is appreciated.
>
> Do I have to copy the types defined in the schema to
> the wdsl file ?
> Do I have to generate the java classes for the types
> separately ?
>
> This is what I see in the console
>
> {http://webservices.groove.net/Groove/2.0/Core/}GrooveRequestHeader
> already exis
> ts
> {http://webservices.groove.net/Groove/2.0/Core/}>GrooveRequestHeader
> already exi
> sts
> {http://webservices.groove.net/Groove/2.0/Core/}GrooveResponseHeader
> already exi
> sts
> {http://webservices.groove.net/Groove/2.0/Core/}>GrooveResponseHeader
> already ex
> ists
> {http://webservices.groove.net/Groove/2.0/Core/}URIList
> already exists
> {http://webservices.groove.net/Groove/2.0/Core/}IDList
> already exists
>
>
> Thanks
>
>
>
> ____________________________________________________
> Start your day with Yahoo! - make it your home page
> http://www.yahoo.com/r/hs
>
>