Conventions Used in This tutorial - Web Services

Text and Code

We observe code guidelines described in Scott Ambler's naming convention (www.ambysoft.com). Where elements are subject to interpretation, we have left the choice up to each author. To avoid ambiguity, we employ full method signatures throughout the tutorial, including empty parentheses after the name of a no-argument method. The sole exception to this practice is for overloaded methods, such as println. The vocabulary in this tutorial conforms to the Java, UML, and design patterns usage. Where appropriate, we use nonstandard Java terminology (after first alerting the reader), coin a new term, or take exception to the official definition.

The terms app server, server, and J2EE app server are used inter-changeably. Unless otherwise noted, these terms all refer to a J2EE app server.

For additional information on UML, we recommend UML Distilled and Unified Modeling Language User Guide.

Graphics

The graphical conventions used here are based on the Unified Modeling Language (UML) standard. UML is a modeling language for object-oriented and component-based development. Only subsets of the UML diagrams are used. The three primary UML diagrams used and of interest to our readers are use cases, sequence diagrams, and class diagrams. Use cases show interactions, class diagrams depict the static structure of classes, and sequence diagrams show dynamic object interaction. Because different notations can be used to represent the same model, Figures P.1 through P.3 illustrate how we use these UML conventions. Screenshot P.1 illustrates the connectors, arrows, and other elements in a standard UML class diagram, along with different types of associations.