Java Reference
In-Depth Information
element="ns4:author"></part> </message>
<message name="authorSearchResponse">
<part xmlns:ns5="http://ns.soacookbook.com/catalog"
name="searchResults"
element="ns5:searchResults"></part> </message>
<portType name="Catalog">...</portType>
The contents of the
wsdl:portType
are the same for both styles.
Summary
It's worth noting that selecting and specifying the style and use combination is a configuration
matter. It will change the semantics of your service implementation, and you will be able to
identify differences in your WSDL, but overall the usability should be transparent to deve-
lopers; it doesn't change how your service appears to behave.
The main lesson is this: interoperability can either be enhanced or thwarted depending on the
combination you specify here, primarily because it affects your schema. When possible, for
the sake of interoperability and validation, I encourage you not to rely on tools to generate
your schemas for you. Rather, design your service from the schema up. This will help you to
focus the idea of your SOA as an infrastructure for enterprise integration via document ex-
change. This will in turn encourage you to keep individual service implementations focused
on their core business logic and allow you to move decorating business logic into orchestra-
tions.
