Step 3: Take a Look

You'll notice that we exported the war artifact that was created by Enunciate to the file "ifyouwannabecool.war" (with the option "-Espring.war.file ifyouwannabecool.war"). Drop that into your favorite J2EE container and hit the app in a browser to see what you've got!

(For the majority of you who aren't actually performing the steps, you can see the static elements by clicking here.)

The first thing you'll notice is a nice-looking web page with a generic title divided into two sections. The first section describes the SOAP API, and it includes the two services we just wrote. The second section is the data section describing our domain. You'll notice the WSDL that was generated as well as the schema that describes our domain. (Note that the WSDL is consolidated, containing definitions of both endpoints because they service the same namespace.)

As you continue to poke around, you'll notice that the documentation is quite sparse (although some information can be gleaned from the names of the methods and arguments).

The "downloads" page links to client-side binaries and source code that will access your SOAP API. These client-side libraries were generated by Enunciate and packaged up (along with everything else) in the war. The client-side code is clean, intuitive, and powerful, handling all the complexities of the API, including the faults (populating even the fields of the faults), the complex data structures, one-way operations and even leveraging MTOM to handle the binary data.

Oh, and of course the endpoints are deployed as described in the WSDL.