This week's book giveaway is in the OCAJP 8 forum. We're giving away four copies of OCA Java SE 8 Programmer I Study Guide and have Edward Finegan & Robert Liguori on-line! See this thread for details.
Long time ago, I thought of preparing for the SCDJWS exam and I was going through the tutorials for SOAP and I did not want to explore any furthur as it had too many information that I had to keep in mind in order to sit for the exam and also I was not working on Webservices at thost times. But very recently I will be kind of having a chance to work on webservices and I came acorss axis and I quickly read through the apache site and came to know that with Axis I do not have to deal anymore with SOAP by myself as Asis is an abstraction over it. I just cannot believe this. I mean I did not find any concrete information from the Apache website that could substantiate my conclusion. So that was why I was asking here if anyone has already worked on it to provide me with some information. But however like you said I will skim through this forum for any related posts on Apache AXIS.
Joined: Mar 22, 2005
Axis (versions 1 and 2) has always used SOAP, but you -as the developer- never had to create or handle the actual XML. So I'm not sure what you mean by "I do not have to deal anymore with SOAP by myself".
The service contract (WSDL in the case of a SOAP web service) is central to everything the service does. Usage of graphical tools to design the SOAP web service contract is encouraged. However you need a good understanding of XML, XML Namespaces, XML Schema, SOAP, and WSDL in order to design an effective WSDL that defines the supported SOAP messages.
Once you have your SOAP web service contract's WSDL you can use tools like Axis's WSDL2Java, Axis2's WSDL2Java, or JAX-WS's wsimport (Creating a service from WSDL) to generate a service skeleton. The generated code will exhibit Logic-to-Contract coupling - this is considered acceptable however because this type of coupling doesn't propagate any implementation or logic coupling to the service consumer.
So competent SOAP web services developers have to have a good understanding of XML, XML Namespaces, XML Schema, SOAP, and WSDL plus any of the WS-* standards that they may be using. [ November 30, 2008: Message edited by: Peer Reynders ]