axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joe Plautz" <>
Subject Re: Best Practices?
Date Wed, 12 May 2004 14:01:48 GMT
My first attemps have started with a WSDL/Schema then I generate everything.
I was able to find an example at and I just manipulate it to the way
I need it. I thought this to be the best way at the time because of

>From what I've been finding thus far there are no "Standard" practices, just
"Accepted" practices. Starting with a class then using Java2WSDL and then
WSDL2Java seems to be the most common. But, it almost seems that this was
not the intention of the designers of Axis. Why use two steps when you can
use one? Creating a WSDL from scratch seems like the intended way, but is
not the most accepted way by the developers/users of Axis. Why write what
you can generate?

I know this isn't difficult earth shattering stuff, I'm just looking for the
best way of doing this. So, when I start working with other people to create
services, we're doing it the "right" way.

----- Original Message ----- 
From: "Dorner Thomas" <>
To: <>
Sent: Wednesday, May 12, 2004 7:01 AM
Subject: AW: Best Practices?

You are right - if you will do a interoperable webservice
that deal with other clients (.Net ...) its better to go from the

But when i use String, int and so on and i generate a wsdl by
java2wsdl, I hope the wsdl i get, depends on the standard spec.
for wsdl!????

So there should no problem to use the wsdl by other languages!???

Dont know how it looks with complex datatypes!????

Do you all write your own wsdl by hand????


-----Urspr√ľngliche Nachricht-----
Von: David Cunningham []
Gesendet: Mittwoch, 12. Mai 2004 13:14
Betreff: RE: Best Practices?

I disagree, the right way is to start with your WSDL and schema files. If
you want any hope of being WS-I compliant or using doc/literal this is your
best bet. As soon as you start with an interface, you start dealing Java
types that do not correlate to schema types very well. For example, if you
use: public List getStuff() or public String[] getStuff(), you will either
generate a WSDL file that can't be parsed properly by other consumers (.NET,
Glue, etc) or be bound to Java collection types that have no chance of being
parsed properly by .Net (without a lot of hacking around).

My recommendation, again personal preference, is always give thought to the
XML that is going across the wire and what you are trying to send/receive
and in what structure. This is especially important when dealing with
doc/literal since you are sending a single document over the wire.

- david

-----Original Message-----
From: Dorner Thomas []
Sent: Wednesday, May 12, 2004 2:03 AM
To: ''
Subject: AW: Best Practices?

The right way is to write a interface which includes all the Methods your
webservice should offer.

Then you use java2wsdl to generate your wsdl. You have to correct your
parameternames in your auto generated wsdl, cause the the params looks like
in0, in1, in2... .

Then you use wsdl2java to generate your stub, locator, skeleton, impl and
maybe a testclient.

Now you can implement and deploy your Service by unsing the addtional
generated .wsdd files.

Hope this helps you


-----Urspr√ľngliche Nachricht-----
Von: Joe Plautz []
Gesendet: Dienstag, 11. Mai 2004 18:48
Betreff: Best Practices?

I'm a newbie looking for guidance in creating WebServices with Axis. I've
gone through the documentation backwards and forwards and have come up with
me own ways of doing things. I start with a WSDL that I create and use
WSDL2Java to generate the code and go from there. What I'm looking for is a
best practices because I don't feel confident in the way I am going about

Do most people start from a WSDL? Do people generate a WSDL from an
interface and go from there? Do people just create a class and a WSDD file?
Or, do people use JWS files that accept a string and the string contains xml
formated text?

If there are any sites that cover this information, please forward them on
to me.

Any help will be appreciated!!!

Joe Plautz

View raw message