HydraExpress creates two server classes for each portType, a message handling skeleton class and an implementation base class. The port must have an associated wsdl:binding that contains a soap:binding element. In the typical case, the soap:binding element has a transport attribute that specifies the HTTP transport: transport="http://schemas.xmlsoap.org/soap/http".

The name of the skeleton class is based on the port binding name with the string Skeleton appended. The WSDL file shown above would create one skeleton class for each of the two portType elements (lines 1 and 4). The class names would be based on the binding names (lines 2 and 5), resulting in the classes GetSkiReportSOAPBindingSkeleton and GetInternationalSkiReportSOAPBindingSkeleton.

The name of the implementation base class is based on the portType name with the string Base attached. The WSDL file shown above would create one implementation base class for each of the two portType elements (lines 1 and 4 resulting in the classes GetSkiReportBase and GetInternationalSkiReportBase..

HydraExpress also generates a sample implementation class for each implementation base class. The sample implementation class derives from the base class, and its name is the base class name with the final Base changed to Imp. For the above example, these classes would be GetSkiReportImp and GetInternationalSkiReportImp.