James,
I have
used a variety of tools/platforms(webMethods, Axis, Eclipse, Sun's Studio
Creator, Sun's WSDP, .Net, webSphere) to do some very very basic
interop testing. I found that the differences are sometimes minor and sometimes
a bit more trouble. The differences range from certain xml types not
being supported or misinterpreted, namespace interpretation issues,
interpretation of styles ie doc/literal versus doc/literal wrapped etc.
I
found this resource to be very helpful in getting started with WSDL first
design. The author talks about some of the interop issues towards the
end.
http://devresource.hp.com/drc/slide_presentations/schemaWSDL/index.jsp#introduction.
I haven't found that there are a ton of resources available when it comes
to WSDL design, best practices and design patterns. I do know that
the most trouble I have had is when using any vendor's tool to generate WSDL
based off existing implementations. I'm not an XML expert by any stretch
of the imagination but I have seen that the more complex the xml schemas are the
more likely its not going to work across all of the
platforms.
If you
are looking for a pretty decent WSDL editor at a great price(free) you can check
out my recent blog entry on the Eclipse
3.1 with WTP 1.0 http://darth.homelinux.net .Don't
know about you but I find hand editing WSDL to be a bit prone to error, of
course that could be just my concentration abilities.
markg
-----Original Message-----
From: James Clinton [mailto:[EMAIL PROTECTED]
Sent: Friday, February 24, 2006 10:05 AM
To: [email protected]
Subject: RE: wsdl2java or java2wsdlThanks Mark.I not just talking about Axis specific services.I'm interested to here more about your interop problems you have experienced. Are you certain these occurred because the WSDL was generated, also was this using Axis' java2wsdl or some other SOAP servers tools?James-----Original Message-----
From: Griffin, Mark [mailto:[EMAIL PROTECTED]
Sent: 24 February 2006 13:25
To: [email protected]
Subject: RE: wsdl2java or java2wsdlJames, are you talking about a specific to Axis question about why you would design your interface prior to writing the implementation or are your talking about a more general best practice when it comes to web services?I'm not sure if there is any technical advantage that is particular to Axis that would lead you down one path or the other. But from an overall design best practice (there aren't a lot when it comes to web services in my opinion) when developing interfaces, I think it is generally best to start with your XML schemas first and then move into a modular WSDL approach. The goal is to have a more robust extensible interface that is going to be more interoperable with other technologies. There are some resources on this subject in particular talking about interoperability issues ie which types have issues on which platforms, the various levels of support for the basic profile and all of the ws-* standards. This practice also takes the platform out of the picture and focuses more on the service being provided. Hopefully leading you down the path to a more abstract interface.Designing the classes first might mask some problems that will crop up later with other platforms even though Axis might not have an issue with it. I have personally run into interoperability issues with a lot of the major platforms out there when generating wsdl from existing interfaces. Of course if you have no goals for interoperability with other platforms and you don't care about abstract and loosely coupled interfaces then it probably doesn't matter and you probably don't need to be using web services to begin with. :) Just my two cents.markgMark E. Griffin
-----Original Message-----
Developer Services
Progress Energy
From: James Clinton [mailto:[EMAIL PROTECTED]
Sent: Friday, February 24, 2006 6:27 AM
To: [email protected]
Subject: RE: wsdl2java or java2wsdl
Thanks for that, but you haven't answered my question.I too build from the WSDL up, but what I would like to know is what are the 'advantages/dis-advantages in doing this'?James-----Original Message-----This should be an FAQ. Many people, myself included, recommend java2wsdl only as starting point. Once you have a basic wsdl, start using that as your template and from then on use wsdl2java. I myself skip the java2wsdl part and start editing a new wsdl. Some people, though, do prefer to use java2wsdl to get started.
From: robert lazarski [mailto:[EMAIL PROTECTED]
Sent: 23 February 2006 18:13
To: [email protected]
Subject: Re: wsdl2java or java2wsdl
HTH,
Robert
http://www.braziloutsource.com/
On 2/23/06, James Clinton <[EMAIL PROTECTED]> wrote:Are there any significant advantages in building an Axis Web Services from the WSDL (wsdl2java), as apposed from the Java (java2wsdl) ?James
-----------------------------------------------------
THE INFORMATION IN THIS E-MAIL AND IN ANY ATTACHMENTS IS CONFIDENTIAL
AND MAY BE PRIVILEGED OR OTHERWISE PROTECTED FROM DISCLOSURE.
IF YOU ARE NOT THE INTENDED RECIPIENT AND HAVE RECEIVED IT IN ERROR YOU ARE ON NOTICE OF ITS STATUS.
PLEASE NOTIFY THE SENDER IMMEDIATELY BY RETURN EMAIL AND THEN DELETE THIS EMAIL AND ANY ATTACHMENT FROM YOUR SYSTEM.
YOU MUST NOT RETAIN, COPY OR USE THIS E-MAIL OR ANY ATTACHMENT FOR ANY PURPOSE, NOR DISCLOSE ALL OR ANY PART OF ITS CONTENTS TO ANY OTHER PERSON:
TO DO SO COULD BE A BREACH OF CONFIDENCE
EMAIL MAY BE SUSCEPTIBLE TO DATA CORRUPTION, INTERCEPTION AND UNAUTHORISED AMENDMENT,
AND WE DO NOT ACCEPT LIABILITY FOR ANY SUCH CORRUPTION, INTERCEPTION OR AMENDMENT OR THE CONSEQUENCES THEREOF.
WE MAY MONITOR THE CONTENT OF EMAILS SENT AND RECEIVED VIA OUR NETWORK FOR VIRUSES OR UNAUTHORISED USE AND FOR OTHER LAWFUL BUSINESS PURPOSES.
WE DO NOT ACCEPT RESPONSIBILITY FOR ANY LOSS OR DAMAGE ARISING FROM A VIRUS IN ANY EMAIL OR ATTACHMENT.
-----------------------------------------------
[EMAIL PROTECTED]
