| UML element | Validation process |
|---|---|
| Package or model | The transformation processes nested packages, components, classes, and interfaces in the package or model specified as the transformation source. |
| Component | The stereotype that is applied to a component,
if any, determines how the transformation validates it. Usage of the
stereotypes from the Services Modeling (SoaML) profile
or the deprecated Software Services profile
is optional. For more information about the transformation output, see the related reference topic below. |
| Interface | The stereotype that is applied to an interface,
if any, determines how the transformation validates it. Usage of the
stereotypes from the Services Modeling (SoaML) profile
or the deprecated Software Services profile
is optional. For more information about the transformation output, see the related reference topic below. |
If the source model or source model elements do not contain enough information to describe a Web service, the WSDL document that the UML-to-WSDL transformation generates is incomplete. For example, if a UML interface in the source model does not contain any operations, the generated WSDL document will not have WSDL messages. In this example, the transformation only creates the empty PortType.
You can specify a project or folder as a target for the output that the UML-to-WSDL transformation generates.
You can use class diagrams to visually develop WSDL elements. You can also edit WSDL elements in the diagram editor or in the Properties view.
You can customize existing bindings or create bindings by using the transformation extensibility framework.
The UML-to-WSDL transformation supports all bindings described in the Web Services Description Language (WSDL) 1.1 W3C Note 15 March 2001, in addition to the Wrapped Document Literal binding. The transformation supports versions 1.1 and 1.2 of SOAP.
For each interface in the transformation source, you can specify the binding and SOAP version in the Properties view on the WSDL Port page, or when you create or edit a UML-to-WSDL transformation configuration.
You can use transformation extensions to extend and enhance custom transformations or the transformations that are available in the IBM Rational modeling products. You can create new transformation extensions or use extensions associated with installable features. To run a transformation extension, you must first enable the transformation extension in the target transformation configuration.
This content applies to version 7.5.4 or later. If you have installed the feature for IBM Rational Modeling for Communications Applications, you can enable a transformation extension to generate ParlayX specification-conformant WSDL when transforming ParlayX models using the UML-to-WSDL transformation.
The transformation provides integration functionality with IBM Rational Team Concert, CVS, Rational ClearCase®, and Rational ClearCase LT version control systems, which enables you to automatically check out files or add new files. You must enable team capabilities to work with configuration management systems.