axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Anne Thomas Manes <>
Subject Re: Question about generated Java w/ WSDL2Java
Date Wed, 25 May 2005 13:43:46 GMT
A few recommendations:

Things work a lot more easily if you use the "wrapped" style rather
than "unwrapped". In the "wrapped" style, the input element name must
be the same as your operation name. So, for the GetPurpose operation,
you input element should be called GetPurpose rather than

In your definitions <types> section, you create a schema with the
targetNamespace of "", and then you
import the same namespace, which is not a valid construct. You should
<include> it rather than <import> it. Alternatively, you can define
the schema's targetNamespace to be the same as your WSDL namespace and
use the <import>. Regardless of the approach, the schema elements will
remain assigned to the "" namespace.

In your services <binding>, you should not specify a namespace
attribute on the <input> and <output> definitions. (You use the
namespace attribute only when using rpc style.

I'm pretty sure that the bug that caused the generation of the
extraneous ">" characters in the WSDD has been fixed. Please make sure
you are using Axis 1.2 final.


On 5/25/05, Kador, Daniel <> wrote:
> Hi,
> I hope this won't be too long, but I've got a few questions.  I've got
> my WSDL broken into two parts - definitions and services.  I've attached
> them below, as well as the schema I'm using.
> Using the command "java -s -S true
> AIEstateService.wsdl", I generate the Java code with stubs and a
> skeleton.  My question lies in the realm of what is actually generated.
> I've also attached the generated deploy.wsdd, so you can see what I'm
> talking about.
> As an aside, if I try to deploy this service and run a test client on
> it, I get the following error: "No such operation 'GetPurposeRequest'"
> (obviously this happens when I attempt to use the GetPurposeRequest()
> function).
> I assumed the problem might be in the deploy.wsdd.  In some of the
> typeMappings, the qname value has an (I think) extraneous '>'.  It's my
> understanding that this is not correct, and in fact makes the WSDD
> invalid, but I'm certainly not sure, as I can deploy the service and
> view its WSDL through the Axis web interface with no problems.
> Does anybody have any insight into what I'm doing wrong, or how to fix
> the problems I'm having?
> Thanks,
> Dan

View raw message