UML-to-WSDL transformations

You can create UML representations of Web services and run the UML-to-WSDL transformation to generate Web Services Description Language (WSDL) documents. WSDL documents are files that have .wsdl as a file name extension.

Valid sources for the UML-to-WSDL transformation

The UML-to-WSDL transformation generates WSDL documents from the following UML sources. You can select multiple elements as the source of the transformation:
  • Models
  • Packages
  • Components
  • Interfaces

Validation of source model elements

The following table lists the UML elements that the transformation validates when you run the transformation.
Important: Elements in models that were created by using IBM® Rational® modeling products version 7.5.4 or earlier might have stereotypes from the Software Services profile applied. The Software Services profile is deprecated and a profile called the Services Modeling (SoaML) profile is available for modeling services. For information about migrating from the Software Services profile to the Services Modeling (SoaML) profile, see the related link at the end of this topic. For information about how stereotypes in the Software Services profile map to stereotypes in the Services Modeling (SoaML) profile, see the related link at the end of this topic.
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.

Valid targets for the UML-to-WSDL transformation

You can specify a project or folder as a target for the output that the UML-to-WSDL transformation generates.

Visual representations of WSDL elements in class diagrams

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.

Creation of custom bindings

You can customize existing bindings or create bindings by using the transformation extensibility framework.

Supported WSDL bindings and SOAP versions

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.

WSDL transformation extensions

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.

Integration with team support

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.


Feedback